skills.rest
harsh-pandhe
harsh-pandheCOMMUNITY
Explore all skills by this author →
Website𝕏@HarshPandheGitHub

writing-plans

Generate a structured implementation plan from a written specification.

Updated Aug 23, 2026
Search Tags:#planning#documentation#software-engineering#version-control#task-decomposition#implementation-plan
One-click install
npx skills add https://github.com/harsh-pandhe/pod-transit --skill writing-plans-harsh-pandhe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/harsh-pandhe/pod-transit/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/harsh-pandhe/pod-transit --skill writing-plans-harsh-pandhe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate a specification or requirements into a complete, actionable implementation plan, ensuring everyone understands the scope, tasks, and deliverables before coding begins.

Core Features & Use Cases

  • Structured planning: Converts specs into a decomposition of tasks with file changes, tests, and documentation.
  • Guided execution plan: Provides step-by-step tasks, including commit messages and review checks.
  • Documentation and handoff: Produces a plan that supports execution handoff and traceability for audits.

Quick Start

Review a project spec and generate a complete, executable implementation plan saved 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 convert a software specification into an actionable implementation plan?▼

To convert a software specification into an implementation plan, you define a structured decomposition of tasks that outlines required file changes, testing strategies, and commit messages. This ensures the entire team understands the scope before coding begins.

What is task decomposition for software engineering features?▼

Task decomposition for software engineering features is the process of breaking down a written specification into file-by-file impacts, testing strategies, and documentation. It provides a guided execution plan with clear task boundaries for feature additions or bug fixes.

Can I create a reproducible workflow with checklists for a codebase refactor?▼

Yes, you can create a reproducible workflow with checklists for a codebase refactor by generating a structured plan from your specification. The plan guides execution step-by-step, including documentation, review checks, and commit messages for traceability.

Does structured planning work for bug fixes across any codebase?▼

Structured planning works for bug fixes across any codebase with clear task boundaries. It translates the specification into file-by-file impacts and testing strategies, ensuring the required changes are documented and testable before implementation.

What's the best way to document file-by-file impacts before coding begins?▼

The best way to document file-by-file impacts before coding is to generate a structured implementation plan saved to your documentation directory. This plan outlines required files, tests, and commits, supporting execution handoff and traceability for audits.

Related Skills

Explore More Software Engineering Skills→
ccakmak60ccakmak60
1

writing-plans

Convert vague specifications into actionable engineering implementation plans with required files, tests, and save path to docs/superpowers/plans.

Community
Advanced
kgadekkgadek

writing-plans

Generate implementation plans with file paths, tests, and version-control commands.

Community
Advanced
m19803261706m19803261706

cx-fix

Investigate, fix, test, and commit code changes with conventional commits.

Community
Intermediate
fmbetancourtfmbetancourt

speckit-tasks

Generate dependency-ordered task lists from spec.md and plan.md design artifacts.

Community
Intermediate