plan

Provide the raw ticket as input and the Skill runs a five-phase pipeline: reading the code, challenging scope, reviewing architecture and tests, then saving README, ARCHITECTURE, TASKS, and TESTS files. Big architecture questions are asked one at a time before the blueprint is written.

The plan produces up to four markdown files: README with decisions and a component manifest, ARCHITECTURE with data contracts and failure cases, TASKS with a layered work breakdown, and TESTS with codepath diagrams and gap analysis. TESTS.md is skipped when the project has no test setup.

No. The Skill is strictly read-only against source code and may only write handoff files through the kit_save_handoff tool. This separation prevents planning and implementation from degrading each other.

Every proposed new component must climb a reuse ladder: check if it is needed, search the repo by behavior, then consider stdlib, framework features, and existing dependencies. Each CREATE entry in the manifest must cite the search proving nothing existing fits.

The handoff phase offers four options: execute the plan immediately, delegate it to Gemini, Claude, or Codex, stop, or revise. Parallel execution groups tasks by dependency layers into batches run by separate agents.