What problem does it solve? Turning a high-level product vision into an actionable, prioritized backlog and release plan is slow and inconsistent when done ad hoc. This Skill structures that work by generating schema-conformant backlog stubs and promoting them into release files only when needed. ## Core Features & Use Cases - Backlog Generation (Mode A): Decomposes product vision into epics and lightweight story stubs in .archflow/backlog.yaml, with an epic index in .archflow/roadmap.yaml. - Just-in-Time Release Planning (Mode B): Promotes selected stubs into .archflow/releases/{slug}.yaml with acceptance criteria, subtasks, and design/contract gates derived from story scope. - Stable Story Identity: Story IDs are epic-scoped and never change across promotion, and stories live in exactly one file at a time. - Use Case: After a product-strategist defines goals in .archflow/project-context.md, run this role in Phase 1 to produce the full backlog, then carve a first release from high-priority stubs when the team is ready to build. ## Quick Start Ask the agent to act as the Archflow feature-planner and generate the initial backlog and roadmap from the product vision in .archflow/project-context.md.
