skills.rest
ARounder-183
ARounder-183COMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Writes detailed multi-step implementation plans with TDD tasks and exact file paths.

92|12|Updated Dec 21, 2025
Search Tags:#workflow#tdd#markdown#code generation#task breakdown#implementation plan#software planning
One-click install
npx skills add https://github.com/ARounder-183/HiFiShifter --skill writing-plans-arounder-183
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ARounder-183/HiFiShifter/tree/main/.github/skills/writing-plans
Command: npx skills add https://github.com/ARounder-183/HiFiShifter --skill writing-plans-arounder-183

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or feature idea into code often fails because engineers lack context about the codebase, conventions, and testing approach. This Skill converts requirements into a comprehensive, bite-sized implementation plan that any developer can execute without prior knowledge of the project. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - Exact File Paths and Code: Every task specifies exact files to create or modify, complete code snippets, and exact commands with expected output. - Execution Handoff: After saving the plan to docs/plans/, it offers subagent-driven execution or a parallel session with an executing-plans workflow. - Use Case: You have a feature spec for a new API endpoint. Use this Skill to produce a dated plan document with ordered TDD tasks, exact file paths, and commit steps ready for execution. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan for your feature spec before writing any code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan before coding a feature?▼

Start from a spec or requirements document, then break the work into bite-sized tasks of 2-5 minutes each. Each task lists exact files to create or modify, a failing test, the minimal implementation, verification commands, and a commit step.

What is a good task granularity for TDD implementation plans?▼

Each step should be one action taking 2-5 minutes: write the failing test, run it to confirm failure, write minimal code to pass, run tests to confirm success, then commit. This keeps progress verifiable and reversible.

Where should implementation plan documents be saved?▼

Plans are saved as Markdown files under docs/plans/ using the naming pattern YYYY-MM-DD-feature-name.md. Each plan starts with a header stating the goal, architecture, and tech stack.

When should I not write a detailed implementation plan?▼

Skip detailed planning for trivial single-step changes or exploratory spikes where the approach is unknown. The plan format assumes a defined spec and multi-step task; over-planning tiny edits adds overhead without benefit.

How are implementation plans executed after writing?▼

Two options exist: subagent-driven execution in the same session with a fresh subagent per task and review between tasks, or a parallel session using an executing-plans workflow with batched checkpoints.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

brainstorming

Shape vague product ideas into clear design directions before implementation.

Community
Advanced
christopherarterchristopherarter
90

superpowers-writing-plans

Translate software specifications into structured development plans with tests and commits.

Community
Advanced
ulpi-ioulpi-io
13

plan-founder-review

Review engineering plans against codebase reality and deliver verdicts.

Official
Advanced
mcevoyinitmcevoyinit

speedrun

Automate rapid code construction with minimal planning and enforced security rules.

Community
Intermediate