Build prototype component by component

Build prototype components with discovery-plan validation

When you have a validated discovery plan and layout and need to build prototype components one at a time with continuous validation against the plan.

• · Discovery Plan (markdown file in exploration/discovery-plans/)
• · Layout direction (optional, from exploration/captures/layout-direction.md)
• · Dispatch Strategy (from dashboard: copilot-cli|claude-subagents|direct)

• · Built prototype components in working tree or branch
• · Component review artifacts (plan alignment + quality checks)
• · Merge/PR options presented to SME

• · orba/superpowers execution discipline plugin (required)
• · superpowers:using-git-worktrees for isolation
• · superpowers:requesting-code-review for two-stage review
• · superpowers:test-driven-development for validation
• · superpowers:finishing-a-development-branch for merge

• · Discovery Plan exists in exploration/discovery-plans/
• · exploration-workflow orchestrator or dashboard exists
• · If Phase 2 enabled: layout-direction.md exists

• · Missing Discovery Plan: stops and reports missing file
• · Orchestrator dispatch verification fails: returns to dashboard
• · Stale dispatch token: hands back to orchestrator

• · Verifies Discovery Plan exists before proceeding
• · Two-stage component review (plan alignment, then quality check)
• · Test-driven development invoked for each component
• · Orchestrator dispatch validation prevents stale executions