writing-plans

Create implementation-ready plans with task breakdowns, file mappings, and test steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams formalize multi-step tasks into comprehensive, executable plans before touching code, reducing ambiguity and rework.

Core Features & Use Cases

  • Plan decomposition: maps every task to specific files, tests, and documentation, ensuring nothing is missed.
  • Reusable templates: provides structured blueprint for recurring feature types to accelerate planning.
  • Handoff readiness: generates a clear execution plan that engineers and reviewers can follow with confidence.

Quick Start

Create a complete implementation plan for a given feature by outlining tasks, required files, tests, and commit steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan from a software requirement spec?

To create an implementation plan from a software requirement spec, map every task to specific files, tests, and documentation using structured task decomposition, ensuring traceable milestones and handoff readiness before coding begins.

What is task decomposition in software project management?

Task decomposition in software project management breaks down multi-step features into executable plans, mapping each unit to specific files, required tests, and documentation artifacts to eliminate ambiguity and reduce development rework.

How do I break down a multi-step coding task into executable milestones?

Break down a multi-step coding task into executable milestones by applying plan decomposition templates that map tasks to specific files, tests, and commit steps, generating a structured blueprint for reviewers and engineers.

Do I need a complete feature spec before generating an implementation plan?

You need a complete feature spec or requirements document before generating an implementation plan, as the planning process scopes tasks, maps files, and defines testing artifacts based directly on those existing requirements.

What's the best way to formalize multi-step software tasks before coding?

The best way to formalize multi-step software tasks before coding is using reusable blueprint templates that enforce structured planning, file mapping, and explicit task breakdowns to achieve handoff readiness.

When should I avoid automated plan generation for software engineering?

Avoid automated plan generation for software engineering when a spec or requirements document does not exist, as the process relies on task scoping and file mapping from existing requirements to generate traceable milestones.