Captain Claude Code — Testing skill for Claude Code

Captain Claude Code (CCC) ⚓

**A Claude skill that takes a non-technical founder from a product idea to a working product — in one guided, mostly-autonomous run.**

You describe what you want to build (or hand CCC a design/system spec). CCC plans the build in phases, executes and independently verifies each phase itself, and only stops when a step genuinely needs *your* hands — creating an account, pasting an API key into a `.env` file, clicking a deploy button. Every stop comes with a plain-English why, the exact link, and click-by-click steps.

Born from a real shipped project: a WeChat mini-program built end-to-end by a student founder with no coding background, using this exact workflow.

What it does

• Interactive intake — CCC greets you and asks: "Do you have a design or system spec, or should we create one together?" Every question is answerable by a non-technical person, but each answer lets CCC make a real engineering decision (it asks "will people share things with each other?", not "SQL or NoSQL?").
• Senior-engineer analysis behind the scenes — user scale, per-user data privacy and security, system design, and "is this shippable or just a demo," with online research when decisions depend on current tools or pricing.
• A phased plan ordered by risk — the scariest unproven assumption (payments, a platform API) is tackled first, so surprises come early and cheap.
• An autonomous build loop with honest verification — every phase's work is graded by a separate verifier that never saw the implementation, against written, testable acceptance criteria. Failures are fixed and re-verified automatically; you're only interrupted for product decisions.
• An append-only decisions log — every non-obvious choice, its rejected alternatives, and the why, so nothing gets silently reversed later.
• Progress you can read — regular status blocks: what CCC is working on now, real percent complete, what's next, and whether it needs anything fro