writing-plans

Create implementation plans with tasks, file paths, tests, and verification steps.

97|8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/peteromallet/megaplan --skill writing-plans-peteromallet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/peteromallet/megaplan/tree/main/megaplan/agent/skills/software-development/writing-plans
Command: npx skills add https://github.com/peteromallet/megaplan --skill writing-plans-peteromallet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates complex specifications into actionable, trackable implementation plans that guide developers and reviewers to deliver results.

Core Features & Use Cases

  • Bite-sized Task Granularity: decompose work into 2-5 minute steps with explicit actions, files, and tests.
  • Comprehensive Plan Artifacts: produce exact file paths, test scaffolds, docs references, and commit messages.
  • Reproducible Execution: enable hands-on execution by subagents with clear verification steps, ownership, and acceptance criteria.

Quick Start

Provide a complete implementation plan from a given spec, including tasks, files, tests, and verification steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break a software feature spec into bite-sized implementation tasks?

An implementation plan translates complex specs into trackable, bite-sized tasks with exact file paths, test scaffolds, and verification steps to guide hands-on execution and reviews.

How do I create a reproducible workflow for subagent development?

Create a reproducible workflow by detailing task-by-task instructions, 2-5 minute steps, and commit-ready changes that enable hands-on execution by subagents with clear ownership.

Can I use this implementation planning approach for database migrations?

Yes, implementation planning applies to multi-step software features, migrations, and design rewrites by breaking work into bite-sized tasks with comprehensive plan artifacts and verification steps.

What is the best way to plan TDD documentation for a multi-step feature?

Plan TDD documentation by generating a comprehensive plan artifact that includes exact file paths, test scaffolds, documentation references, and commit messages alongside the task breakdown.

Does this task planning method generate commit messages for each step?

Yes, the task planning method produces comprehensive plan artifacts that include commit-ready changes and messages to ensure each bite-sized task is ready for version control integration.