skills.rest
cpp-for-everything
cpp-for-everythingOFFICIAL
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with tasks, file mappings, and acceptance criteria.

1|Updated Mar 8, 2024
Search Tags:#planning#versioning#documentation#software-engineering#task-decomposition#plan-writing
One-click install
npx skills add https://github.com/cpp-for-everything/ORM --skill writing-plans-cpp-for-everything
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/cpp-for-everything/ORM/tree/main/.windsurf/skills/writing-plans
Command: npx skills add https://github.com/cpp-for-everything/ORM --skill writing-plans-cpp-for-everything

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineering teams convert vague specs or requirements into comprehensive, actionable implementation plans before touching code, ensuring alignment and reducing rework.

Core Features & Use Cases

  • Plan Decomposition: Break down complex features into clear tasks, files, and milestones.
  • Structured Plan Templates: Provide standardized plan formats including tasks, tests, and commit messages.
  • Documentation & Handover: Generate plan docs stored at docs/superpowers/plans for versioning and handoffs.

Quick Start

Create a detailed implementation plan for a given feature and save it 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 turn high-level specs into actionable implementation plans?▼

Implementation plans generated from specs include task decomposition, risk assessment, testing strategy, and cross-team coordination to guide software development and reduce rework.

What should a software feature implementation plan include for cross-team coordination?▼

Comprehensive plans include scope, file mappings, acceptance criteria, testing approach, and versioned storage under docs/superpowers/plans to facilitate documentation and handoffs.

When do I need task decomposition for software engineering projects?▼

Task decomposition is required for multi-step features needing structured breakdowns into tasks, files, and milestones to ensure alignment and reduce rework.

How do I write a structured plan template for feature development?▼

Structured plan templates provide standardized formats including tasks, tests, and commit messages, stored as versioned documents for documentation and handovers.

Does converting specs to plans work for complex multi-step features?▼

Yes, it applies to multi-step features requiring task decomposition, risk assessment, testing strategy, and cross-team coordination to ensure comprehensive implementation planning.

What is the best way to document implementation plans for team handoffs?▼

Using versioned storage under docs/superpowers/plans with structured plan templates ensures comprehensive documentation and smooth handovers across engineering teams.

Related Skills

Explore More Software Engineering Skills→
youyouheyouyouhe
4

bid-software-design

Generate high-level and detailed software design documents from requirement specifications.

Community
Advanced
JamkrisJamkris
86

agentic-engineering

Coordinate AI agents to implement software tasks with eval-first verification.

Community
Advanced
PhucMPhamPhucMPham

plans-kanban

Serve a Kanban dashboard for plan.md-based plans with progress and timelines.

Community
Advanced
wayne930242wayne930242
16

agent-architect

Classify knowledge tasks and delegate them to appropriate Claude Code skills via the Skill tool.

Community
Advanced