skills.rest
yuma588
yuma588COMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate structured implementation plans listing files, tests, and docs.

2|Updated Jan 7, 2026
Search Tags:#planning#documentation#implementation#spec#plan#software#task-breakdown
One-click install
npx skills add https://github.com/yuma588/skill-gallery --skill writing-plans-yuma588
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/yuma588/skill-gallery/tree/main/skill-gallery-deploy/skills/community/superpower/writing-plans
Command: npx skills add https://github.com/yuma588/skill-gallery --skill writing-plans-yuma588

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenting every detail of a multi-step task before touching code helps teams coordinate, reduce rework, and ensure a shared understanding of requirements, tests, and deliverables.

Core Features & Use Cases

  • Create a complete, task-level implementation plan that identifies files to touch, tests to write, and docs to review.
  • Provide a ready-to-execute sequence of steps that a developer can follow, ensuring DRY, YAGNI, and TDD practices.
  • Save the plan to a centralized location for traceability (docs/plans/YYYY-MM-DD-<feature-name>.md) and enable quick handoffs between teammates.

Quick Start

Create a detailed implementation plan for the given feature and save it 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
What is an implementation plan for software development and when do I need one?▼

An implementation plan documents task-level execution steps, files to touch, and tests to write before coding. You need one for cross-functional feature development, complex requirements, or scenarios with incomplete specs to align engineers on scope.

How do I create a detailed task breakdown for a multi-step coding project?▼

To create a task breakdown, generate a structured plan listing touched files, testing steps, and documentation needs. This provides a ready-to-execute sequence ensuring DRY, YAGNI, and TDD practices for developers to follow.

How do I structure documentation for feature implementation plans to ensure team alignment?▼

Structure implementation documentation by listing touched files, tests, and deliverables, then save the plan to a centralized path like docs/plans/YYYY-MM-DD-<feature-name>.md. This enables traceability and quick handoffs between teammates.

Can I use task-level planning for cross-functional features with incomplete specs?▼

Yes, task-level planning is specifically designed for scenarios with incomplete specs and cross-functional feature development. It generates a detailed execution plan that aligns engineers on scope and deliverables before coding begins.

What is the best way to document software implementation steps for developer handoffs?▼

The best way to document implementation steps for handoffs is generating a structured plan with testing steps and documentation needs, saving it to docs/plans/YYYY-MM-DD-<feature-name>.md. This reduces rework and ensures shared understanding.

Related Skills

Explore More Product & Management Skills→
poko8nadapoko8nada

planning

Guide teams to gather requirements, define MVP scope, and break down tasks.

Community
Intermediate
underPressueunderPressue

writing-plans

Converts a project specification into a step-by-step implementation plan with tasks, files, tests, and milestones.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
Colten-CovingtonColten-Covington

project-management

Guide project scope, risk assessment, and delivery planning.

Community
Basic