writing-plans

Generate step-by-step implementation plans for multi-step software development tasks.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tc9011/my-skills --skill writing-plans-tc9011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tc9011/my-skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/tc9011/my-skills --skill writing-plans-tc9011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers create detailed, step-by-step implementation plans for multi-step tasks, ensuring clarity and reducing the need for prior context.

Core Features & Use Cases

  • Detailed Task Breakdown: Generates bite-sized tasks for engineers, including specific file modifications, code snippets, and testing instructions.
  • Contextual Documentation: Assumes minimal prior knowledge of the codebase or problem domain.
  • Use Case: When starting a new feature, use this Skill to generate a comprehensive plan that guides an engineer through writing tests, implementing code, and committing changes.

Quick Start

Use the writing-plans skill to create an implementation plan for adding user authentication.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate a step-by-step implementation plan for a new software feature?

To generate a step-by-step implementation plan, provide your multi-step software development task to this tool. It outputs detailed file modifications, code snippets, and testing procedures for engineers with zero codebase context.

What's the best way to break down multi-step software development tasks for engineers without codebase context?

The best way to break down multi-step tasks is using automated task breakdown. This process generates bite-sized tasks detailing specific file modifications, code snippets, and testing instructions, assuming minimal prior codebase knowledge.

How does automated implementation planning handle TDD, DRY, and YAGNI principles?

Automated implementation planning enforces TDD, DRY, and YAGNI principles by structuring the generated output. It dictates writing tests first, avoiding duplication in code snippets, and limiting modifications strictly to required functionality.

Can I use this task breakdown tool for complex multi-step tasks without prior domain knowledge?

Yes, you can use this task breakdown tool for complex multi-step tasks without prior domain knowledge. It provides contextual documentation and assumes minimal prior knowledge of the codebase or problem domain.

What should an implementation plan include for guiding engineers through coding and committing changes?

An implementation plan should include detailed task breakdowns with specific file modifications, code snippets, testing procedures, and commit instructions. This ensures engineers can execute coding tasks without needing additional context.

When do I need an automated implementation plan instead of writing documentation manually?

You need an automated implementation plan when starting a new feature that requires comprehensive guidance through testing, implementing code, and committing changes. It ensures clarity and reduces the manual effort of writing documentation for multi-step tasks.