writing-plans

Transform project specs into structured task-by-task implementation plans.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/rakaadi/agent-kit --skill writing-plans-rakaadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/rakaadi/agent-kit/tree/main/skills/writing-plans
Command: npx skills add https://github.com/rakaadi/agent-kit --skill writing-plans-rakaadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams need to translate vague specs into concrete, auditable work plans, this Skill provides structured, step-by-step guidance to convert requirements into actionable tasks and deliverables.

Core Features & Use Cases

  • Generate end-to-end implementation plans from specs for zero-context engineers.
  • Break complex requirements into bite-sized tasks with clear artifacts, testing, and documentation steps.
  • Save and version plans under docs/plans with a date stamp for reproducibility and traceability.

Quick Start

Provide the feature name and a brief spec, and the writer will generate a complete implementation plan saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn project requirements into a structured implementation plan?

To turn project requirements into an implementation plan, provide a feature name and brief spec to generate a step-by-step task breakdown. This process converts vague requirements into auditable, bite-sized engineering tasks with clear deliverables.

How do I break down complex software features into actionable engineering tasks?

To break down complex software features into actionable engineering tasks, this tool splits multi-step requirements into granular items. Each generated task includes explicit steps for testing, documentation, and commits for end-to-end execution.

What is the best way to ensure reproducible execution of software implementation plans?

Reproducible execution of software implementation plans is achieved by saving generated documents under docs/plans with a date stamp. This structured versioning approach ensures traceability and reproducibility for engineering teams.

Can I generate end-to-end implementation plans for engineers with no project context?

Yes, you can generate end-to-end implementation plans specifically designed for zero-context engineers. The output provides comprehensive task-by-task guidance, ensuring engineers can execute features without prior background knowledge.

Does this implementation plan generator require any external dependencies?

No, this implementation plan generator does not require any external dependencies to function. It operates independently to transform your project specs into structured, task-by-task implementation documents for engineering teams.