writing-plans

Convert high-level specs into detailed executable software plans.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/sixscripts-ai/ghostssh --skill writing-plans-sixscripts-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/sixscripts-ai/ghostssh/tree/main/skills/writing-plans
Command: npx skills add https://github.com/sixscripts-ai/ghostssh --skill writing-plans-sixscripts-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan multi-step software tasks from a high-level spec into a detailed, executable plan.

Core Features & Use Cases

  • Generate end-to-end task breakdowns, including files to touch, code, tests, and documentation.
  • Enforce DRY, YAGNI, and TDD workflows while delivering bite-sized tasks designed for frequent commits.
  • Save plans to a dedicated worktree location and adapt plans as requirements evolve.

Quick Start

Provide a feature brief and I will generate a complete 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 executable software implementation plan from a high-level spec?

To generate a software implementation plan from a high-level spec, provide a feature brief to produce a detailed task breakdown. The plan covers scope, file touchpoints, tests, and documentation across subsystems, saving outputs to a dedicated worktree location with versioned naming.

What is the best way to break down multi-step software tasks for frequent commits?

The best way to break down multi-step software tasks for frequent commits is to enforce DRY, YAGNI, and TDD workflows. This approach delivers bite-sized tasks designed specifically for frequent commits and adapts plans as requirements evolve.

Can I use task decomposition to plan code, tests, and documentation simultaneously?

Yes, you can use task decomposition to plan code, tests, and documentation simultaneously. The process generates end-to-end task breakdowns that explicitly map out files to touch, required code changes, necessary tests, and documentation updates.

Do I need a requirements document before planning multi-step software tasks?

You need a feature brief or high-level spec before planning multi-step software tasks. Providing a feature brief allows the plan generation process to translate the requirements into a detailed, executable plan covering subsystem scope and file touchpoints.

Where are generated software implementation plans saved?

Generated software implementation plans are saved to the docs/superpowers/plans directory. The system uses versioned naming for these files and integrates with planned workflows to adapt the output as requirements evolve.