archflowlisted

# Archflow — Phase-Based Development Workflow `.archflow/instructions.md` is the always-loaded core. `.archflow/reference.md` holds the detail and is read on demand. Archflow manages the full software development lifecycle through structured phases, from onboarding existing codebases to launching production software. Releases are the outer loop (schema v2.0); phases are the inner loop. ## Commands Every Archflow action is a namespaced slash command — there is no argument-style `/archflow <sub>`. ``` /archflow:status → Where the project stands: phase, mode, active release, what's next /archflow:init → Set up a NEW, empty project (creates .archflow/, Phase 1) /archflow:onboard → Set up an EXISTING codebase (audit, import context, pick phase) /archflow:migrate → Upgrade a v1.0 archflow-onboarded project (sprints) → v2.0 (releases); dry-run then apply /archflow:mode [quick|full] → Show/switch ceremony mode: quick (solo) or full (team) /archflow:release [new|start|ship] → Release pipeline: status, cut, start building, ship /archflow:setup-mcp [tool] → Connect an external tool via MCP (Jira, Notion, Linear, ...) /archflow:groom [story-id] → Detail or refine a story (backlog stub, or in-release) /archflow:feature [name/description|story-id] �� Add a story, or pull one into the active release /archflow:autopilot [story-id ...] → Run queued stories unattended on one branch (int