writing-plans

Turn high-level tasks into step-by-step implementation instructions by expanding them with explicit file paths, complete code samples, and verification commands. This Skill takes vague tasks like 'implement authentication' and breaks them into bite-sized (2-5 minute) steps with exact files to create, code to write, and tests to run.

The best way is to systematically expand each task with concrete artifacts: exact file paths, complete code examples, and measurable verification steps. This eliminates ambiguity and ensures engineers can execute without guessing about which files to modify or what code to write.

Verify your plan by investigating the current codebase state against assumptions before execution. The Skill uses a codebase-investigator workflow to surface mismatches early, ensuring your expanded steps remain accurate and prevent off-track work.

Yes. You can expand single tasks, task ranges, or entire epics from existing checklists into detailed implementation guides. Each expansion is presented for user approval before updating, ensuring alignment before work begins.

Apply task-first TDD when generating detailed steps to ensure each implementation step includes verification commands and measurable outcomes. This cadence produces concrete, testable artifacts rather than ambiguous instructions.

The Skill applies across diverse engineering contexts—frontend, backend, infrastructure—by generating context-specific file paths, code samples, and verification commands for each step, maintaining consistency while adapting to the domain.