skills.rest
ironbob
ironbobCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert high-level specs into task-level implementation plans with file and test mappings.

Updated Mar 21, 2026
Search Tags:#planning#worktree#software-engineering#task-decomposition#plan-template#planning-automation#plan-document
One-click install
npx skills add https://github.com/ironbob/SuperPower_light --skill writing-plans-ironbob
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ironbob/SuperPower_light/tree/main/skills/writing-plans
Command: npx skills add https://github.com/ironbob/SuperPower_light --skill writing-plans-ironbob

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Plans helps teams convert high-level specs into concrete, auditable implementation plans. It guides engineers to map tasks, files, tests, and documentation, ensuring nothing is missed.

Core Features & Use Cases

  • Plan decomposition: break a feature into concrete tasks with clear ownership and artifacts.
  • Worktree-aware planning: generate plans that reference dedicated worktrees for isolated development.
  • Template-driven execution: produce consistent plan headers, sections, and checkpoints for repeatable work.
  • Use Case: convert a product spec into a step-by-step plan detailing changed files, tests, and docs.

Quick Start

Create a comprehensive implementation plan for a new feature, listing tasks, affected files, tests, and acceptance criteria.

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 task plan?▼

To convert a software specification into an actionable task plan, you map high-level requirements into concrete tasks, detailing affected files, tests, and acceptance criteria for clear ownership and execution.

What is worktree-aware planning for new features?▼

Worktree-aware planning generates implementation plans that reference dedicated worktrees, ensuring isolated development environments for specific features, refactors, or cross-team coordination tasks.

How do I break down a large refactor into trackable implementation tasks?▼

You break down a large refactor into trackable implementation tasks by decomposing the spec into discrete units, mapping each unit to specific file changes, required tests, and documentation updates.

Does this planning approach require a dedicated worktree context?▼

Yes, generating these implementation plans requires a dedicated worktree context to ensure task decomposition and file mapping are accurately scoped for isolated software engineering workflows.

What is the best way to ensure consistent plan generation across multiple software engineering projects?▼

The best way to ensure consistent plan generation is using a repeatable plan-template workflow that produces standardized plan headers, sections, and checkpoints for every new feature or refactor.

Related Skills

Explore More Software Engineering Skills→
forecast-bioforecast-bio
27

featree

Create a feature branch in a dedicated git worktree with crosslink hooks and agent identity.

Official
Advanced
fall-out-bugfall-out-bug
19

review

Validate completed workstreams against quality gates and traceability requirements.

Community
Intermediate
romiluz13romiluz13
161

build-workflow

Automate software feature builds with TDD and subagent orchestration.

Community
Intermediate
Lands-1203Lands-1203
40

f2s-doc-milestone

Generate project milestones from requirements, git history, and task completion.

Community
Advanced