What problem does it solve? Teams using the Archflow phase-based development framework need a structured way to capture new features, place them in the right epic and release, and start git work without losing traceability between roadmap files and branches. ## Core Features & Use Cases - Feature capture wizard: Add a story by name, free-text description, or by importing an epic/story link from Jira, Linear, Notion, or GitHub via MCP. - Backlog vs. release routing: Append a lightweight stub to backlog.yaml or a fully detailed story with gates, acceptance criteria, and subtasks to the active release file. - Pull-forward workflow: Promote an existing backlog story into the active release, grooming it first when needed. - Git workflow setup: Create the feature branch from main, update current-phase.yaml and current-feature.yaml, and mark the story in_progress. - Use Case: A developer runs /archflow-feature "users can reset their password via email" and gets a new story under the right epic, placed in the active release, with a feature branch ready for Phase 3 implementation. ## Quick Start Ask your agent to run /archflow-feature followed by a feature name or description, for example "/archflow-feature user notifications", to add the story and optionally start its feature branch.
