skills.rest
robertpelloni
robertpelloniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate execution-ready implementation plans with exact files, tests, and verification steps.

2|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/robertpelloni/workspace --skill writing-plans-robertpelloni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/robertpelloni/workspace/tree/main/AI_COORDINATION/skills/superpowers-skills-main/skills/collaboration/writing-plans
Command: npx skills add https://github.com/robertpelloni/workspace --skill writing-plans-robertpelloni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of creating comprehensive and executable plans for complex initiatives. It ensures all necessary steps, resources, and potential obstacles are considered, leading to more successful project outcomes.

Core Features & Use Cases

  • Structured Planning: Generate plans with clear objectives, steps, and success criteria.
  • Dependency Mapping: Identify and manage inter-task dependencies.
  • Use Case: Before starting a major software upgrade, use this skill to generate a detailed project plan outlining phases, tasks, responsible teams, timelines, and potential risks.

Quick Start

Write a detailed plan for migrating our database from MySQL to PostgreSQL.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a project plan that engineers can execute immediately?▼

Generate comprehensive implementation plans from complete designs that include bite-sized tasks with exact files, tests, docs, and verification steps. The Skill produces execution-ready plans saved as structured markdown documents with standardized headers, ensuring engineers with zero codebase context can start work immediately.

What should a plan include for feature development, bug fixes, and refactors?▼

Effective plans map dependencies between tasks, specify exact files to modify, include test cases and documentation updates, and define verification steps. Plans follow DRY, YAGNI, and TDD principles with frequent commits, ensuring all necessary steps and potential obstacles are considered upfront.

Can I use planning to manage complex software upgrades and migrations?▼

Yes. Plans work across any project scope, from database migrations to major upgrades. Structure objectives, phases, task dependencies, timelines, and risk identification to ensure all teams understand their responsibilities and potential blockers before execution begins.

How do I organize plans so my team can reference and track them?▼

Plans are saved to a standardized location—docs/plans/YYYY-MM-DD-<feature-name>.md—with consistent headers and structured task formatting. This organizational approach makes plans discoverable, trackable, and easy for teams to reference throughout execution.

What's the difference between a planning document and an executable implementation plan?▼

Implementation plans go beyond high-level strategy: they specify exact files, include test coverage requirements, document changes needed, and outline verification steps for each task. This level of detail eliminates ambiguity and enables immediate execution without design decisions during development.

Related Skills

opsmillopsmill
9

speckit-specify

Translate natural language feature descriptions into testable specification documents.

Official
Advanced
yuanyuekejiJNyuanyuekejiJN
18

executing-plans

Execute written implementation plans in ordered batches with review checkpoints.

Community
Intermediate
FFCfelps1FFCfelps1

ce-work

Plan, execute, and ship software features with code review and CI/CD integration.

Community
Advanced
yknothingyknothing
1

sprint-planning

Translate capacity, priorities, and risks into an executable sprint plan.

Community
Intermediate