skills.rest
franroa
franroaCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with exact file paths, code samples, tests, and verification steps.

Updated Oct 22, 2025
Search Tags:#TDD#software development#task breakdown#implementation plan#code examples#developer guidance#engineering workflow
One-click install
npx skills add https://github.com/franroa/chezmoi --skill writing-plans-franroa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/franroa/chezmoi/tree/main/dot_opencode/superpowers/skills/writing-plans
Command: npx skills add https://github.com/franroa/chezmoi --skill writing-plans-franroa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that implementation plans are so comprehensive and detailed that any engineer, even with zero codebase context, can execute them flawlessly. It prevents ambiguity, reduces questions, and guarantees consistent, high-quality development.

Core Features & Use Cases

  • Bite-Sized Task Granularity: Breaks down implementation into tiny, actionable steps (2-5 minutes each), including writing tests, implementing minimal code, and committing.
  • Exact Instructions: Mandates exact file paths, complete code examples, and precise commands with expected output for every step.
  • Zero-Context Assumption: Forces you to write plans assuming the engineer knows nothing about the toolset or problem domain, eliminating guesswork.
  • Use Case: After a design is complete, use this Skill to create the implementation plan. For example, if you need to add a new feature, this Skill will guide you to write a plan that specifies every file to touch, every line of code, and every test command, making execution effortless.

Quick Start

Announce skill usage

I'm using the writing-plans skill to create the implementation plan.

The skill will then guide you to structure the plan with detailed tasks.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a detailed implementation plan that engineers can execute without knowing the codebase?▼

Implementation plans break down features into bite-sized tasks with exact file paths, complete code samples, test commands, and verification steps. This approach ensures any engineer can execute the plan end-to-end without ambiguity, even with zero codebase context.

What should a task breakdown include for TDD-based development?▼

A TDD task breakdown specifies test code first, then implementation code, with precise commands and expected output for each step. This enforces test-driven development by ensuring tests validate each feature increment before moving to the next task.

How do I structure an implementation plan to avoid rework and scope creep?▼

Structure plans by applying DRY and YAGNI principles—write only the code necessary for each step, avoid duplication, and commit frequently in small increments. Detailed specifications for each task prevent overengineering and keep scope focused.

Can I use implementation plans to document features for team execution?▼

Yes. Implementation plans serve as executable documentation that specify exact commands, file modifications, tests, and commit history. Teams can reference these plans to execute features consistently without additional clarification or rework.

What's the difference between a design document and an implementation plan?▼

A design document describes what to build and why; an implementation plan details exactly how to build it with runnable code blocks, file paths, test commands, and step-by-step verification. Plans are actionable blueprints ready for execution.

Related Skills

Explore More Software Engineering Skills→
RedWoodOGRedWoodOG
174

writing-plans

Convert software specifications into executable implementation plans with tasks and code samples.

Community
Advanced
arozumenkoarozumenko
18

implement-feature

Convert approved feature requirements into code using test-driven development.

Community
Intermediate
rajitsaharajitsaha
10

commit

Run quality gates, review diffs, update docs, and create structured commits.

Community
Basic
nicepkgnicepkg
276

agile-sprint-planning

Define sprint goals, estimate user stories, and manage the sprint backlog.

Official
Intermediate