writing-plans

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

⭐36stars🔀6forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

The Writing Plans skill for Claude streamlines software development by generating granular, high-precision implementation roadmaps. It is specifically designed to assist engineers—even those with zero prior codebase context—by breaking down complex designs into bite-sized tasks. By providing exact file paths, complete code snippets, and precise testing commands, this skill ensures high-quality execution while strictly adhering to TDD, DRY, and YAGNI principles. It serves as a critical bridge between high-level architecture and actual code implementation, enhancing productivity for both human developers and AI subagents.

Use Cases

  • Developer Onboarding: Quickly generate step-by-step implementation guides for new team members, allowing them to contribute to complex projects immediately without extensive manual walkthroughs.
  • AI Agent Orchestration: Create structured, actionable task lists that can be dispatched to AI subagents for autonomous execution, ensuring consistency and reducing errors.
  • Technical Debt & Refactoring: Produce detailed plans for refactoring legacy modules, specifying every file change and validation step to maintain system integrity.
  • Test-Driven Development (TDD) Enforcement: Ensure code quality by defining exact test commands and expected outputs for every task before the implementation phase begins.
  • Complex Feature Rollouts: Bridge the gap between design documents and production code by translating architectural requirements into a sequence of 2-5 minute micro-tasks.
nameWriting Plans
descriptionWriting for zero-context engineers, code completeness, test design patterns
when_to_usewhen design is complete and you need detailed implementation tasks for engineers with zero codebase context
version2.2.0
level1
- pathreferences/best-practices.md
titleBest Practices & Guidelines

Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the Writing Plans skill to create the implementation plan."

Context: This should be run in a dedicated worktree (created by brainstorming skill).

Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md

Quick Reference

Plan header template: See Plan Structure & Templates

Task template: See Plan Structure & Templates

Granularity guide: Each step = 2-5 minutes. See Best Practices

Core Principles

  • Exact file paths always - Not "in the user module" but "src/models/user.py"
  • Complete code in plan - Not "add validation" but show the validation code
  • Exact commands with expected output - "pytest tests/file.py -v" with what you'll see
  • Reference relevant skills - Use @ syntax: @skills/category/skill-name
  • DRY, YAGNI, TDD, frequent commits - Every task follows this pattern

For detailed guidance: Best Practices & Guidelines

Execution Handoff

After saving the plan, offer execution choice:

"Plan complete and saved to docs/plans/<filename>.md. Two execution options:

1. Subagent-Driven (this session) - I dispatch fresh subagent per task, review between tasks, fast iteration

2. Parallel Session (separate) - Open new session with executing-plans, batch execution with checkpoints

Which approach?"

If Subagent-Driven chosen:

  • Use @skills/collaboration/subagent-driven-development
  • Stay in this session
  • Fresh subagent per task + code review

If Parallel Session chosen:

  • Guide them to open new session in worktree
  • New session uses @skills/collaboration/executing-plans

Remember

  • Write for zero-context engineers (specify everything)
  • Complete code blocks, not instructions
  • Exact commands with expected output
  • Test first, then implement, then commit
  • Reference existing patterns in codebase
  • Keep tasks bite-sized (2-5 minutes each)

Need examples? See Plan Structure & Templates for complete task examples.

Need patterns? See Best Practices for error handling, logging, test design, and more.