writing-plans

Translate specifications into structured implementation plans with task breakdowns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create comprehensive implementation plans from a spec or requirements before touching code, clarifying scope, tasks, files, tests, and docs to prevent rework.

Core Features & Use Cases

  • Transforms vague specs into detailed task breakdowns with responsible owners, required files, testing steps, and documentation updates.
  • Enforces planning discipline (DRY, KISS, TDD) by producing bite-sized tasks and checkpoints that engineers can execute.
  • Use Case: When given a feature spec, generate a complete plan that guides development, testing, and release.

Quick Start

Provide a project spec or requirements and I will generate a complete, step-by-step implementation plan.

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 from a feature spec?

To generate an implementation plan from a feature spec, provide your project specifications or requirements. The tool translates them into a structured, step-by-step breakdown covering tasks, files, tests, and documentation.

What is task decomposition in software development planning?

Task decomposition in software development planning breaks vague specifications into bite-sized, actionable checkpoints. It enforces DRY, KISS, and TDD principles to clarify scope, responsible owners, and required file changes before coding begins.

How do I structure multi-step engineering tasks before coding?

Structure multi-step engineering tasks by generating a plan stored under docs/superpowers/plans with date-stamped filenames. This ensures a consistent plan structure guiding development, testing, and release from start to finish.

Do I need a complete specification to create an implementation plan?

You do not need a complete specification to create an implementation plan, but providing project specs or requirements yields the best results. The tool transforms available inputs into detailed task breakdowns to prevent rework.

Does automated planning work for small software development tasks?

Automated planning works for small software development tasks by enforcing planning discipline through bite-sized tasks and checkpoints. It applies to any project requiring task decomposition, file changes, tests, and docs.

When should I not use a structured implementation plan?

You should not use a structured implementation plan for trivial changes requiring no task decomposition, file changes, tests, or documentation updates. It is designed for multi-step work needing scope clarification and rework prevention.