From discuss-and-execute
Runs the full discuss-and-execute pipeline end-to-end with minimal human intervention. Gather context, automated panel discussion with three technical stakeholders, plan waves, execute, and pre-ship audit — all in one invocation. <triggers> /autopilot, run autopilot, full pipeline, end to end, run everything, autopilot mode, hands-off implementation </triggers>
How this skill is triggered — by the user, by Claude, or both
Slash command
/discuss-and-execute:autopilotThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the full pipeline front-to-back: gather context, panel discussion, plan waves, execute, audit.
Run the full pipeline front-to-back: gather context, panel discussion, plan waves, execute, audit.
Human approval is requested only at two gates: after the panel produces its recommendations, and after the pre-ship audit. Everything else runs automatically.
---
config:
layout: elk
---
graph LR
A["/autopilot [work]"] --> B{".context/codebase/?"}
B -->|No| C["/gather-context"]
B -->|Yes| D["Use existing map"]
C --> D
subgraph PANEL["Panel Discussion"]
E["3 stakeholder agents"] --> W1["Wave 1: positions"]
W1 --> W2["Wave 2: debate"]
W2 --> CONSENSUS["Consensus"]
end
D --> E
CONSENSUS --> F["User approves"]
F --> G["/plan-waves"]
G --> H["/execute"]
H --> AUDIT["/audit"]
AUDIT -->|PASS| DONE(["Shipped"])
AUDIT -->|FAIL| FIX["Fix"] --> AUDIT
Check if .context/codebase/ exists and is current.
/gather-context automatically — spawn 4 mapper agents, write 7 docs, verify. No human approval needed.Codebase map current — skipping gather-context.If work description provided as argument, use it. Otherwise ask:
What should autopilot build?
This is the only open-ended question. Everything after this is automated.
Run /discuss --auto [work description].
This spawns three AI stakeholders who debate the implementation approach across 2+ waves, then produce consensus recommendations in .context/CONTEXT-<SLUG>.md and a full transcript in .context/DISCUSSION_LOG-<SLUG>.md.
See /discuss Auto Mode for the full panel discussion process.
Human gate: After the panel completes, present the consensus summary and wait for approval before continuing to planning.
Run /plan-waves with the slug from Step 3. The planner receives the panel's consensus, conventions, and concerns. No human approval needed — the panel already debated the structure.
Print the plan summary when done:
Plan generated: .context/PLAN-<SLUG>.md
[N] waves, [M] tasks
Run /execute with the slug. All waves dispatched automatically. Cross-review runs per wave. Fix cycles run automatically (max 2 per wave). Commit per wave.
Print wave-by-wave progress:
Wave 1: [theme] — [N] tasks dispatched... complete (0 fix cycles)
Wave 2: [theme] — [N] tasks dispatched... complete (1 fix cycle)
...
Run the pre-ship audit from /execute Step 5:
If FAIL: fix automatically (up to 2 attempts), then re-audit. If still failing after 2 attempts, pause and present failures to user.
If PASS: report completion.
Autopilot complete: [work description]
Pipeline: gather-context -> panel (3 stakeholders, [N] waves) -> plan -> execute -> audit
Waves executed: [N/N]
Tasks completed: [M/M]
Pre-ship audit: PASS
Files changed:
[consolidated list]
Artifacts:
- .context/CONTEXT-<SLUG>.md (decisions)
- .context/DISCUSSION_LOG-<SLUG>.md (panel transcript)
- .context/PLAN-<SLUG>.md (wave plan)
npx claudepluginhub emmahyde/dotfiles --plugin discuss-and-executeProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.