jbr870/devwork-skills
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Dev journal path mismatch between /develop and learning-analysis/simplify-report #3

New issue
Closed
opened 2026-04-20 16:44:01 +00:00 by jbr870 · 1 comment
jbr870 commented 2026-04-20 16:44:01 +00:00
Owner
Copy link

Problem

The producer and consumers of dev journals disagree on where journals live.

Producer — develop/SKILL.md (line 197) writes dev journals to:

$FEATURE_FOLDER/dev-journal-WU-N.md

i.e. at the feature folder root, per work unit.

Consumers look for dev journals in a different, legacy location:

  • closeout/procedures/learning-analysis.md (line 21): 
    All $FEATURE_FOLDER/sreqs/SR-*/dev-journal.md — if teammates wrote journals
  • simplify-report/SKILL.md (line 24): 
    Dev journals in $OUTPUT_DIR/sreqs/SR-*/dev-journal.md — for understanding development context

The sreqs/SR-*/ path reflects an older model where features were decomposed into multiple SREQ files. The current model is one SREQ.md per feature, with work-unit decomposition happening inside /develop at runtime — so sreqs/SR-*/ directories don't exist anymore.

Impact

  • learning-analysis and simplify-report silently find no journals, even when /develop wrote them
  • The primary evidence source for learning analysis is effectively broken
  • Any future parser or cross-feature analytics will inherit this mismatch

Proposed fix

Update consumers to match the current producer path:

  • closeout/procedures/learning-analysis.md step 1: read $FEATURE_FOLDER/dev-journal-WU-*.md (glob for all work-unit journals)
  • simplify-report/SKILL.md: same glob pattern
  • Grep the rest of the skills tree for any other references to sreqs/SR-*/dev-journal and update them

Optional: normalize the naming

While fixing this, worth deciding whether dev-journal-WU-N.md is the right filename pattern, or whether something like journals/dev-WU-N.md (a journals/ subfolder, matching the local-first artifact structure being designed elsewhere) reads more cleanly. Keeping files organized under a journals/ subfolder also keeps the feature folder root uncluttered as more artifact types are added. Non-blocking — the path mismatch fix is what matters.

Related

  • #1 (YAML frontmatter for journals) — depends on a single agreed journal path
  • #2 (Consolidate drifted journal templates) — same family of drift, different axis
## Problem The producer and consumers of dev journals disagree on where journals live. **Producer — `develop/SKILL.md`** (line 197) writes dev journals to: ``` $FEATURE_FOLDER/dev-journal-WU-N.md ``` i.e. at the feature folder root, per work unit. **Consumers** look for dev journals in a different, legacy location: - `closeout/procedures/learning-analysis.md` (line 21): ``` All $FEATURE_FOLDER/sreqs/SR-*/dev-journal.md — if teammates wrote journals ``` - `simplify-report/SKILL.md` (line 24): ``` Dev journals in $OUTPUT_DIR/sreqs/SR-*/dev-journal.md — for understanding development context ``` The `sreqs/SR-*/` path reflects an older model where features were decomposed into multiple SREQ files. The current model is one `SREQ.md` per feature, with work-unit decomposition happening inside `/develop` at runtime — so `sreqs/SR-*/` directories don't exist anymore. ## Impact - `learning-analysis` and `simplify-report` silently find no journals, even when `/develop` wrote them - The primary evidence source for learning analysis is effectively broken - Any future parser or cross-feature analytics will inherit this mismatch ## Proposed fix Update consumers to match the current producer path: - `closeout/procedures/learning-analysis.md` step 1: read `$FEATURE_FOLDER/dev-journal-WU-*.md` (glob for all work-unit journals) - `simplify-report/SKILL.md`: same glob pattern - Grep the rest of the skills tree for any other references to `sreqs/SR-*/dev-journal` and update them ## Optional: normalize the naming While fixing this, worth deciding whether `dev-journal-WU-N.md` is the right filename pattern, or whether something like `journals/dev-WU-N.md` (a `journals/` subfolder, matching the local-first artifact structure being designed elsewhere) reads more cleanly. Keeping files organized under a `journals/` subfolder also keeps the feature folder root uncluttered as more artifact types are added. Non-blocking — the path mismatch fix is what matters. ## Related - #1 (YAML frontmatter for journals) — depends on a single agreed journal path - #2 (Consolidate drifted journal templates) — same family of drift, different axis
jbr870 commented 2026-04-20 19:42:02 +00:00
Author
Owner
Copy link

Fixed by 4ff8a84 — all consumers now glob $FEATURE_FOLDER/dev-journal-WU-*.md and no legacy sreqs/SR-*/dev-journal references remain in the tree.

The optional naming/layout question (journals/ subfolder) split off into #5 to be decided alongside #1 and the broader local-first artifact structure.

Fixed by 4ff8a84 — all consumers now glob `$FEATURE_FOLDER/dev-journal-WU-*.md` and no legacy `sreqs/SR-*/dev-journal` references remain in the tree. The optional naming/layout question (journals/ subfolder) split off into #5 to be decided alongside #1 and the broader local-first artifact structure.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jbr870/devwork-skills#3
No description provided.