writing-plans

Generate end-to-end implementation plans for multi-step software tasks.

793|52|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/corvo007/MioSub --skill writing-plans-corvo007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/corvo007/MioSub/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/corvo007/MioSub --skill writing-plans-corvo007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate comprehensive, end-to-end implementation plans for multi-step tasks before touching code, ensuring a shared understanding and a clear execution path.

Core Features & Use Cases

  • Plan documentation: produces a complete plan document saved to docs/plans/YYYY-MM-DD-<feature-name>.md with a standardized header and task steps.
  • Bite-sized tasks: breaks work into actionable steps (e.g., Write tests, Run tests, Implement code, Commit) to guide deterministic progress.
  • Templates and conventions: enforces Plan Document Header, Task Structure, and Execution Handoff guidance to maintain consistency across features.

Quick Start

Create a complete implementation plan for a new feature and save it to docs/plans/YYYY-MM-DD-<feature-name>.md using the provided template.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan for a multi-step software feature?

An implementation plan breaks feature work into bite-sized tasks like writing tests, running tests, implementing code, and committing. This ensures deterministic progress and shared understanding before touching code.

What is the standard structure for a software implementation plan document?

Implementation plans apply to multi-step software tasks including feature development, bug fixes, and documentation work. They are designed to be handed to engineers across multiple scenarios and teams with zero context.

How do I break down software specifications into actionable engineering tasks?

The generated implementation plan provides execution handoff guidance to maintain consistency across features. This allows engineers to execute the plan deterministically without needing additional context.

Do I need any external dependencies to create task breakdown plans for software engineering?

Implementation plans are saved directly to your local docs/plans directory as markdown files. The standardized save path ensures consistent organization and retrieval of plan documents across your team.