dev-story

Dev Story

Turn a planned story into shipped code. This skill assembles every piece of context an implementing agent needs (story file, current PRD requirement, governing ADR, control manifest, framework conventions), routes the work to the right mobile specialist, and supervises implementation through to test.

Where this lives in the loop:

/qa-plan sprint               -> define test bars before sprint starts
/story-readiness [path]       -> green-light the story
/dev-story [path]             -> THIS skill — implement + test
/code-review [files]          -> review the diff
/story-done [path]            -> verify ACs and close

Output: new or modified files in src/, plus a test file in tests/.

---

Phase 1: Locate the Story

Resolve the story path:

• If a path argument is supplied, read it directly.
• If no argument, open production/session-state/active.md and look for a current story reference. Confirm with the user before proceeding.
• If neither path is available, glob production/epics/**/story-*.md and list every story whose Status: is Ready. Ask the user to pick one.

If the story file does not exist, stop and tell the user to run /create-stories for the relevant epic.

---

Phase 2: Assemble Full Context

Before writing a single line of code, validate that every required input exists. These reads are independent — issue them in parallel.

Artifact	Path	Missing handling
TR registry	docs/architecture/tr-registry.yaml	STOP — tell the user to run /create-epics.
Governing ADR	path from story ADR Governing Implementation: field	STOP — tell the user to run /architecture-decision or fix the path.
Control manifest	docs/architecture/control-manifest.md	WARN — continue but note that layer rules are unchecked.
Framework prefs	.claude/docs/technical-preferences.md	WARN — framework routing falls back to "ask user".

Mark the story BLOCKED in session state and abort if the TR registry or governing ADR is missing.