writing-plans

Generate end-to-end implementation plans for multi-step PROMPT-APP tasks.

1|Updated Feb 10, 2026

Search Tags:#planning #documentation #implementation #engineering #task-decomposition #ttd #plan-document

Ready to run

npx skills add https://github.com/danilonovaisv/PROMPT-APP --skill writing-plans-danilonovaisv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/danilonovaisv/PROMPT-APP/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/danilonovaisv/PROMPT-APP --skill writing-plans-danilonovaisv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming and documenting comprehensive implementation plans for PROMPT-APP tasks, so engineers start coding with a clear, agreed-upon blueprint.

Core Features & Use Cases

Automatically maps task scope to files, tests, and docs, outlining what to touch and in what order.
Produces a structured, step-by-step plan document that follows a consistent header and task format for reliable handoffs.
Ideal for kickoff planning, onboarding new contributors to large features.

Quick Start

Start by generating a complete implementation plan for the requested feature and save it to docs/superpowers/plans/YYYY-MM-DD-writing-plans.md

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 for multi-step engineering tasks?▼

Task decomposition breaks down engineering tasks into explicit, manageable steps. It maps subsystem scope to concrete file changes and test planning, enabling engineers to start coding with a clear, documented blueprint for reliable handoffs.

What is task decomposition and how does it work for software engineering planning?▼

How do I map task scope to specific files and tests before coding?▼

A generated plan document includes a consistent header, explicit tasks, and concrete file changes. It is saved as a markdown file under docs/superpowers/plans/, providing a structured blueprint for implementation and testing.

What format does the generated plan document follow?▼

Can I use implementation plans for onboarding new contributors to large features?▼

Implementation plans are ideal for onboarding new contributors to large features. The plan document provides a structured, step-by-step blueprint with consistent headers and explicit tasks, ensuring reliable handoffs across subsystems.

What's the best way to document test planning across multiple subsystems?▼

The best way to document test planning across subsystems is generating an end-to-end plan. It maps task scope to tests and concrete file changes in a structured document, outlining what to touch and in what order for reliable handoffs.