writing-plans

Create implementation plans with exact file paths and verification commands.

131|4|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill writing-plans-alphalab-ustc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/superpowers/writing-plans
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill writing-plans-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a spec or requirements into a clear, executable implementation plan before any code is changed. It is designed for situations where a task is multi-step, needs careful sequencing, and benefits from detailed testing and file-by-file guidance.

Core Features & Use Cases

  • Comprehensive planning: Breaks work into small, actionable steps with exact file paths and commands.
  • Test-first workflow: Structures tasks around failing tests, minimal implementation, verification, and commit steps.
  • Use case: A developer receives a feature request and needs a worktree-ready plan that another engineer can execute with minimal context.

Quick Start

Use the writing-plans skill to create a detailed implementation plan for this feature request and save it in the appropriate docs/plans file.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a software development spec into an actionable implementation plan?▼

An implementation plan structures multi-step software tasks by breaking work into small, actionable steps with exact file paths, verification commands, and test-first sequencing before any code changes are made.

What is the test-driven workflow for planning code changes in an unfamiliar codebase?▼

The test-driven workflow for planning code changes structures tasks around writing failing tests, performing minimal implementation, running verification commands, and committing steps before developers touch the unfamiliar codebase.

Can I generate a step-by-step build plan for a feature request that another engineer can execute?▼

Yes, you can generate a worktree-ready implementation plan that another engineer can execute with minimal context. The plan stores exact file paths and bite-sized steps in docs/plans for seamless handoff.

Does writing implementation plans work for refactoring and bug fixes, not just feature development?▼

Implementation planning applies to feature development, refactors, bug fixes, and test-driven work. It sequences these multi-step software tasks by requiring exact file paths and verification commands before code changes.

What's the best way to structure an implementation plan for multi-step software tasks?▼

The best way to structure an implementation plan is to use bite-sized steps with exact file paths, pair them with verification commands, apply test-first sequencing, and save the plan in docs/plans.

Do I need exact file paths and verification commands to plan task breakdown for code changes?▼

Yes, exact file paths and verification commands are required prerequisites for task breakdown. The implementation plan mandates these elements to ensure multi-step software tasks are executable and verifiable before code changes.