holoctl-spec-flowlisted

# Spec-Driven Development flow (live plan) This is the canonical pipeline for "user has an idea or external board card → holoctl makes it executable". The spec ticket is created **early** and its body is authored **live** during the discussion — the user watches the plan grow in the dashboard while approval happens in chat: ``` External source (Trello/Linear/Azure/Jira/GitHub/Slack/manual) │ ▼ user pastes content (or future MCP fetches it) /spec ← entry point │ ▼ 1. Intake — detect source_provider/ref/url/label 2. Materialize EARLY — board_create({kind:'spec'}) + skeleton body + status doing 3. Serve & link — ensure the dashboard is up, hand the user the live URL 4. Live authoring loop — discuss in chat; board_update_section after each milestone 5. Review gate — board_move(review) + ask for verbal approval in chat 6. Decompose — parallel-evaluator + boardmaster + board_batch({shared:{parent:SPEC_ID}}) 7. Execute — activate developer/reviewer subagents on the first child task ``` ## When to trigger Fires automatically (auto-trigger via description) when the user: - Pastes a card-like block (with terms like "as a user", "I want", "story:", "acceptance:") OR - Pastes a URL from a known external board (see `holoctl-work-item-router` for patterns) OR - Shares a multi-paragraph request describing work that touches multiple files / modules OR - Explicitly says "vou trabalhar nessa" / "tem esse card aqui" / "vamos planejar essa feature" Doesn't f