skills.rest
YuriiYInno
YuriiYInnoCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Creates detailed implementation plans with bite-sized TDD tasks for engineers with zero codebase context.

Updated Oct 2, 2025
Search Tags:#planning#tdd#react#code generation#task breakdown#implementation plan#nestjs
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill writing-plans-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/writing-plans
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill writing-plans-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into actionable code is risky when the implementing engineer has no context about the codebase. This Skill converts requirements into a comprehensive implementation plan with exact file paths, complete code snippets, test commands, and commit steps, so execution is deterministic and reviewable. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following TDD: write failing test, verify failure, implement minimally, verify pass, commit. - Task Numbering & Storage: Automatically assigns task numbers via a counter file and saves plans to tasks/TASK-{N}/writing-plans-plan.md. - Standard Project Structures: Provides reference layouts for NestJS backends, React frontends, and full-stack monorepos to ground plans in real conventions. - Use Case: After brainstorming a new authentication feature, hand the requirements to this Skill to produce a step-by-step plan that another engineer or AI agent can execute without asking clarifying questions. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan for your feature requirements 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?▼

Provide your spec or requirements and invoke the writing-plans skill. It produces a plan with a goal, architecture summary, tech stack, and tasks broken into 2-5 minute steps covering tests, implementation, and commits.

How to break a feature into bite-sized TDD tasks?▼

Each task follows a five-step loop: write the failing test, run it to confirm failure, write the minimal implementation, run tests to confirm they pass, then commit. Each step is a single action taking 2-5 minutes.

Where are generated implementation plans saved?▼

Plans are saved to tasks/TASK-{N}/writing-plans-plan.md, where N comes from a task counter file or the maximum existing TASK directory number plus one. All generated files use the writing-plans- prefix.

Does the plan include exact file paths and code?▼

Yes. Every task lists exact files to create or modify with line ranges, includes complete code snippets rather than vague instructions, and specifies exact test commands with expected output.

What happens after the implementation plan is complete?▼

The skill stops and offers execution options: implement immediately with the coder skill in the current workspace, or create an isolated workspace with git-worktrees first. The task number is passed along as context.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

brainstorming

Shape vague product ideas into clear design directions before implementation.

Community
Advanced
guanyangguanyang
960

subagent-driven-development

Execute implementation plans by dispatching fresh implementer and reviewer subagents per task.

Community
Advanced
Prathmesh2000Prathmesh2000
1

brainstormer

Explore 2-4 design approaches with trade-offs and a recommended plan.

Community
Advanced
Busboom-FooBusboom-Foo

oop

Apply small code changes directly to master with a deterministic test workflow.

Official
Intermediate