docs(work): scaffold work-system-v1 epic + story

This commit is contained in:
2026-05-13 07:44:54 +02:00
parent 7a080efcb6
commit eac711ecec
2 changed files with 61 additions and 0 deletions

View File

@@ -0,0 +1,33 @@
---
id: 01-state-builder-and-cli
epic: work-system-v1
title: State builder + pnpm work CLI
type: technical-story
status: in-progress
feature: scripts
depends-on: []
blocks: []
---
## Goal
`pnpm work status` shows the current epic/story state across `docs/work/`.
`pnpm work next` prints the next unblocked story. `pnpm work rebuild-state`
regenerates `_state.json` from markdown.
## In scope
- `scripts/work/state-builder.mjs` — pure function, fully tested
- `scripts/work/cli.mjs` — argument dispatch + I/O wrapping the builder
- `docs/work/_state.json` — initial committed snapshot
- pnpm work script entry
## Out of scope
- Per-task state (tasks are markdown checkboxes, not separate entries)
- Orchestrator dispatch logic
- Dependency-graph analysis
## Tasks
- [ ] Epic + story scaffold
- [ ] state-builder.mjs + tests
- [ ] cli.mjs + tests
- [ ] _state.json initial commit + pnpm work script entry
- [ ] Final verification + closeout

View File

@@ -0,0 +1,28 @@
---
id: work-system-v1
prd: null
title: Work system v1 (MVP) — state tracking + pnpm work CLI
type: epic
status: in-progress
features: [scripts]
created: 2026-05-13
---
## Goal
Filesystem-only state tracking for `docs/work/` + a `pnpm work` CLI with
status / next / rebuild-state subcommands. Foundation for future
orchestration; no agent dispatch in v1.
## Why
Agents and humans both need a fast way to see "what's the next unblocked
work?" and "where are we?" — without scanning every story file by hand.
## Out of scope (v2+)
- Sandcastle / agent dispatch
- PRD and ADR elicitation skills
- Decomposer / implementer / reviewer prompts
- DAG analysis (depends-on / blocks)
- Pre-commit hooks (the state file is rebuilt manually for now)
## Stories
- [ ] [01 — State builder + CLI](01-state-builder-and-cli/_story.md)