ff199d6015
When quick-dev infers the intent is an epic story, resolve the full
sprint-status key during step-01's previous-story-continuity sub-step,
then sync sprint-status.yaml at the two workflow boundaries code-review
already owns the trailing half of:
- step-03 start: flip the story to in-progress and lift the parent
epic out of backlog if needed.
- step-05 end: flip the story to review. Code-review keeps ownership
of review -> done.
Resolution uses exact numeric-segment equality on the {epic}-{story}
prefix (never string-prefix match), so 1-1 no longer collides with
1-10. Both sync blocks are idempotent so step-04 loopbacks do not
clobber human edits or bump last_updated without cause. Skips silently
when sprint-status.yaml is missing or the intent is not an epic story.
|
||
|---|---|---|
| .. | ||
| SKILL.md | ||
| compile-epic-context.md | ||
| spec-template.md | ||
| step-01-clarify-and-route.md | ||
| step-02-plan.md | ||
| step-03-implement.md | ||
| step-04-review.md | ||
| step-05-present.md | ||
| step-oneshot.md | ||
| workflow.md | ||