v1: Migration plan — vision to working orchestrator

[maxtechera]

Context

The vision and documentation are complete (VISION.md, WORKFLOW.md, STATE_MACHINE.md). The gap is between what's described and what actually executes. This issue tracks everything needed to ship a working v1.

Current State

Component	Status
SKILL.md, WORKFLOW.md, docs	✅ complete
Board connection (/orchestrator setup)	⚠️ wizard described, not implemented
/orchestrator sweep dispatch	⚠️ skill command exists, no real board reads
Verification engine (separate pass)	⚠️ protocol defined, not wired
8 core domain skills	⚠️ listed in README, content is stubs
Self-improving rules loop	⚠️ designed, not executable
Install paths (Claude Code, ClawHub, manual)	⚠️ documented, untested end-to-end

v1 Milestone — What "Working" Means

A user installs, runs /orchestrator setup, writes a ticket on their board, runs /orchestrator sweep, and gets a verified result with a report posted back to the ticket. No manual intervention required.

Work Required

1. Board connection

• /orchestrator setup wizard writes ~/.config/orchestrator/.env with board credentials
• Validate Linear, GitHub Issues connections via live API call
• Fallback: detect existing MCP server connections before prompting

2. Sweep + dispatch

• /orchestrator sweep reads open tickets from connected board
• Prioritizes by state proximity (Review > Verification > In Progress > Todo > Backlog)
• Matches ticket to domain skill (or default if no match)
• Spawns worker agent with correct skill loaded

3. Verification engine

• Separate verifier pass runs after worker completes
• Runs automated checks defined in ticket's ## Verification section
• Posts verification report back to ticket
• PASS → Done, PARTIAL → Review, FAIL → auto-retry with context

4. Domain skills (core 8)

• content — reels, carousels, blog, newsletter
• ecommerce — product pages, pricing, inventory
• seo — meta tags, sitemaps, structured data
• sales-outreach — sequences, lead sourcing, CRM
• finance — invoicing, AR, KPI scorecards
• growth — ad campaigns, referral loops
• go-to-market — coordinated launches
• engineering — features, bugs, infra (built-in)

5. Self-improving loop

• Rule proposal triggered after repeated failures with same root cause
• /orchestrator rules --pending lists proposed rules
• /orchestrator approve-rule / reject-rule writes to skill file

6. Install + distribution

• End-to-end install test: Claude Code plugin path
• End-to-end install test: clawhub install orchestrator
• End-to-end install test: manual git clone
• Gemini CLI extension manifest validated

Out of Scope for v1

• Dry-run mode
• Metric-gate verification (post-launch checks)
• Cross-ticket dependencies
• Skill marketplace
• Cost tracking dashboard
• Multi-operator / team support

Definition of Done

• Zero-config sweep works on a real board with real tickets
• Verification report is posted to the ticket
• One domain skill (engineering) verified working end-to-end
• Install via git clone works on a clean machine
• README install instructions match actual behavior