writing-plans

Generate implementation plans specifying files, tests, docs, and commit steps.

6|2|Updated Nov 16, 2025

Search Tags:#planning #documentation #TDD #engineering #task-breakdown #implementation-plan

Ready to run

npx skills add https://github.com/EricOo0/stock-trading-platform --skill writing-plans-ericoo0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/EricOo0/stock-trading-platform/tree/main/.codex/superpowers/skills/writing-plans
Command: npx skills add https://github.com/EricOo0/stock-trading-platform --skill writing-plans-ericoo0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers convert vague specs into clear, executable planning steps, enabling fast, consistent start of development work.

Core Features & Use Cases

Structured planning: Produce detailed task-by-task plans that specify touched files, tests, docs, and milestones.
Consistent handoffs: Provide a reusable template for engineers, QA, and leadership.
Use Case: When starting a new feature with limited context, generate a plan that outlines tasks, dependencies, and verification criteria.

Quick Start

Announce at the start that you're using the writing-plans skill, then create a new plan under docs/plans/YYYY-MM-DD-<feature-name>.md using the Plan Document Header.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn vague feature specs into an actionable implementation plan?▼

To turn vague specs into an implementation plan, generate a structured document outlining specific tasks, touched files, required tests, documentation, and milestones for consistent development handoffs.

What is the best way to structure an implementation plan for TDD-oriented engineering?▼

A TDD-oriented implementation plan structures tasks by specifying touched files, verification criteria, tests, documentation, and commit steps to ensure fast, consistent development execution.

How to create a task breakdown for a new feature with limited context?▼

Create a task breakdown by generating a plan document that outlines specific tasks, dependencies, verification criteria, and milestones, ensuring consistent handoffs for engineering and QA.

Can I use this planning template for refactoring and documentation tasks across codebases?▼

Yes, you can use this planning template for refactoring and documentation tasks across codebases by generating comprehensive plans that specify touched files, tests, and commit steps.

Does implementation planning require specific dependencies or component setups?▼

Implementation planning requires no specific dependencies or component setups, allowing you to immediately convert vague specifications into clear, executable planning steps for your engineering tasks.