skills.rest
stabilefrisur
stabilefrisurCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert a spec into a detailed implementation plan with tasks and milestones.

Updated Mar 19, 2026
Search Tags:#planning#documentation#task-decomposition#implementation-plan#planning-templates
One-click install
npx skills add https://github.com/stabilefrisur/panmetis --skill writing-plans-stabilefrisur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/stabilefrisur/panmetis/tree/main/src/panmetis/skills/writing-plans
Command: npx skills add https://github.com/stabilefrisur/panmetis --skill writing-plans-stabilefrisur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex, multi-step software tasks before coding helps engineers align on scope, responsibilities, and milestones, reducing rework and miscommunication.

Core Features & Use Cases

  • End-to-end plan generation: convert a spec into a detailed implementation plan with tasks, owners, and milestones.
  • File structure & task mapping: identify which files to create or modify and how components relate.
  • Plan documentation and handoff: produce a repeatable plan artifact that can be reviewed and handed to execution teams.
  • Quick-start guidance: provide a simple, executable starting point that accelerates plan creation.
  • Example: Given a feature request, generate a plan that breaks it into modules, tests, and documentation.

Quick Start

Create a new implementation plan for a given feature and save it to docs/superpowers/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
How do I break a software feature spec into an implementation plan?▼

To break a feature spec into an implementation plan, this Skill converts requirements into detailed task decomposition, identifying file structures, execution steps, and milestones for software engineering projects.

What is the best way to document task decomposition for a multi-step coding project?▼

Documenting task decomposition is achieved by generating a repeatable plan artifact that maps files to create or modify, ensuring disciplined testing and clear handoff to execution teams.

How do I generate an implementation plan and save it for future reference?▼

You generate an implementation plan from a spec and save it deterministically to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md, providing a quick-start executable artifact for future reference.

Can I use this for complex software engineering projects requiring clear file structure decisions?▼

Yes, you can use this for complex software engineering projects where it enforces precise plan artifacts, file structure decisions, and task-by-task execution steps to reduce rework.

Do I need a complete feature request to start planning multi-step tasks?▼

You need a spec or feature request to start planning multi-step tasks, as the Skill converts this input into comprehensive implementation strategies with modules, tests, and documentation.

Related Skills

Explore More Software Engineering Skills→
datamaker-krdatamaker-kr
1

spec-workflow

Orchestrate specification-driven development from feature idea to implemented code.

Official
Advanced
jlawsjlaws
2

writing-plans

Plans multi-step software tasks with file paths, tests, and commit messages.

Community
Advanced
danmestasdanmestas
4

writing-plans

Convert a detailed spec into a bones-powers implementation plan with tasks and file paths.

Community
Intermediate
DaddyElonMusk69DaddyElonMusk69

plan

Create a detailed development plan and save it as a timestamped markdown file.

Community
Intermediate