skills.rest
rinbarpen
rinbarpenCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from feature specifications.

Updated Jan 12, 2025
Search Tags:#workflow#tdd#markdown#code generation#task breakdown#implementation plan#software planning
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill writing-plans-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/writing-plans
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill writing-plans-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature spec into code without a clear plan leads to missed requirements, inconsistent structure, and untested changes. This Skill converts requirements into a comprehensive, step-by-step implementation plan that any engineer can execute without prior codebase context. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following a strict TDD cycle: write failing test, verify failure, implement, verify pass, commit. - Standardized Plan Format: Produces a Markdown plan saved to docs/plans/ with exact file paths, complete code snippets, exact commands, and expected outputs. - Execution Handoff: Offers subagent-driven execution in the current session or parallel-session execution with an executing-plans skill. - Use Case: Given a spec for a new API endpoint, generate a plan document listing every file to create or modify, the tests to write first, and the commit sequence, ready for task-by-task execution. ## Quick Start Ask the assistant 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?▼

Provide your spec or requirements and invoke the writing-plans skill. It produces a Markdown plan saved to docs/plans/ with a goal, architecture summary, tech stack, and numbered tasks containing exact file paths, code, and test commands.

What is a good task granularity for implementation plans?▼

Each step should be a single 2-5 minute action: write the failing test, run it to confirm failure, implement minimal code, run tests to confirm passing, then commit. This keeps progress verifiable and reversible.

How does test-driven development fit into implementation planning?▼

Every task in the plan follows a TDD cycle: the failing test is written first, then the minimal implementation to pass it, followed by a commit. This ensures each change is verified before moving to the next task.

Can the generated plan be executed automatically?▼

Yes. After saving the plan, you choose subagent-driven execution in the current session with a fresh subagent per task and code review, or a parallel session using an executing-plans skill for batch execution with checkpoints.

When should I not use a detailed implementation plan?▼

Skip formal planning for trivial one-line fixes, exploratory prototypes, or throwaway scripts. The plan format is designed for multi-step features where an engineer with zero codebase context must execute reliably.

Related Skills

Explore More Software Engineering Skills→
josephneumannjosephneumann
4

spec

Transform feature descriptions into structured plans with decomposed tasks and acceptance criteria.

Community
Advanced
AndurilCodeAndurilCode
16

subagent-driven-development

Dispatch subagents for each task with two-stage spec and code quality reviews.

Official
Basic
LaunchPadLabLaunchPadLab
1

feature-review

Review feature specifications for completeness and generate missing Gherkin scenarios.

Official
Intermediate
JNZaderJNZader

nano-mode

Replace the eight-phase SDD pipeline with a four-step inline workflow.

Community
Intermediate