skills.rest
dmulcahey
dmulcaheyCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Converts CEO-approved specs into structured implementation plans with task breakdowns and acceptance criteria.

Updated Mar 16, 2026
Search Tags:#planning#documentation#task-management#software-engineering#spec-to-plan#writing-plans
One-click install
npx skills add https://github.com/dmulcahey/featureforge --skill writing-plans-dmulcahey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/dmulcahey/featureforge/tree/main/skills/writing-plans
Command: npx skills add https://github.com/dmulcahey/featureforge --skill writing-plans-dmulcahey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform CEO-approved specs into comprehensive, implementation-ready plans that guide engineers from discovery to delivery.

Core Features & Use Cases

  • Convert a spec into a structured plan with task breakdowns, ownership, acceptance criteria, and traceability.
  • Provide execution-ready artifacts including design notes, test plans, documentation updates, and rollout steps.
  • Enable consistent planning across multiple teams by enforcing a repeatable plan-format workflow.

Quick Start

Provide the approved spec and the target feature name to generate a complete implementation plan.

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 spec into an implementation plan?▼

To convert a spec into an implementation plan, provide the CEO-approved spec and target feature name to generate structured task breakdowns, ownership details, and acceptance criteria for executable software engineering initiatives.

What should an implementation plan include for complex product initiatives?▼

An implementation plan for complex product initiatives should include task breakdowns, design notes, test plans, documentation updates, rollout steps, and traceability to ensure planning quality from discovery to delivery.

How do I create execution-ready plans for multi-step software features?▼

You create execution-ready plans for multi-step software features by loading an approved spec with proper headers, a plan artifact template, and a defined execution handoff workflow into the planning context to ensure structured delivery.

Do I need a specific spec format to generate a structured implementation plan?▼

Yes, you need a spec with proper headers alongside a plan artifact template and a defined execution handoff workflow to load into the planning context for generating structured, executable implementation plans.

Can I enforce consistent planning across multiple software engineering teams?▼

Yes, you can enforce consistent planning across multiple teams by applying a repeatable plan-format workflow that converts approved specs into structured, traceable implementation plans with standardized execution-ready artifacts.

What is the best way to structure traceability in software implementation plans?▼

The best way to structure traceability in software implementation plans is converting approved specs into structured artifacts with task breakdowns, ownership details, and acceptance criteria mapped directly to the original requirements.

Related Skills

Explore More Software Engineering Skills→
dmulcaheydmulcahey

plan-fidelity-review

Verify draft FeatureForge plans against CEO-approved specs for requirement coverage and topology fidelity.

Community
Advanced
ncsound919ncsound919

writing-plans

Generates a detailed implementation plan with tasks, files, risks, and a step-by-step sequence from a written description.

Community
Advanced
ImaginerLabsImaginerLabs

bmad-agent-dev

Executes approved software development stories with test-driven workflows and CI integration.

Official
Advanced
djwmobleydjwmobley

planning

Decompose specs into actionable implementation plans with traceability.

Community
Advanced