What problem does it solve? Starting a greenfield project or large feature without structure leads to skipped research, reinvented wheels, license conflicts, and unreviewed decisions. This Skill enforces a staged workflow—research, best-practice survey, domain modeling, architecture, review gate, build, and retrospective—so every major decision is investigated and explicitly approved before code is written. ## Core Features & Use Cases - Phased Orchestration: Sequences work through nine stages, delegating each phase to a peer skill (research, domain-modeling, codebase-design, grilling, tdd, code-review, retro) while tracking decisions in a todo list. - Mandatory Review Gate: Batches all open decisions—framework choice, licensing, scope, trade-offs—into one user sign-off checkpoint before building begins. - License & Best-Practice Checks: Surveys mature open-source alternatives before writing code and verifies dependency license compatibility early. - Use Case: A developer starting a large feature says "walk me through the new task flow"; the Skill runs research sub-agents, drafts an architecture, gets explicit plan approval, then drives TDD-based implementation and a closing retrospective. ## Quick Start Explicitly invoke the kickstart skill by name and ask it to walk your new project or large feature through the full research-to-delivery workflow.
