writing-plans

Generate granular implementation plans with file paths, code snippets, and test commands.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/e2662020/QuickMovie --skill writing-plans-e2662020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/e2662020/QuickMovie/tree/main/skills/writing-plans
Command: npx skills add https://github.com/e2662020/QuickMovie --skill writing-plans-e2662020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, incomplete, or poorly tested software implementations that occur when engineers lack full context of a codebase, project requirements, or best practices for breaking down complex tasks and designing tests.

Core Features & Use Cases

  • Granular Task Breakdown: Splits multi-step development tasks into 2-5 minute actionable steps with exact file paths, code snippets, and test commands for each step.
  • Best Practice Enforcement: Embeds core development principles including DRY, YAGNI, and TDD into every plan to ensure high-quality, maintainable code.
  • Clear Execution Handoff: Provides two structured options for implementing the plan, either via subagent-driven development in the current session or parallel execution in a separate worktree.
  • Use Case: When a product team hands off a spec for a new user authentication feature, use this Skill to generate a complete plan covering test writing, implementation, and commits for each component of the feature.

Quick Start

Use the writing-plans skill to generate a step-by-step implementation plan for the new team collaboration feature outlined in the latest product requirements document.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a software feature specification into actionable coding tasks?

Implementation planning breaks down software feature specifications into granular, actionable coding tasks. It splits multi-step development requirements into 2-5 minute steps with exact file paths, code snippets, and test commands to eliminate context gaps for engineering teams.

What is the best way to plan test-driven development for a new feature?

Test-driven development planning embeds TDD principles directly into your implementation plan. It structures the workflow by generating specific test commands and code snippets for each 2-5 minute task, ensuring tests are written and executed before implementation.

How do I create an implementation plan that enforces DRY and YAGNI principles?

To enforce DRY and YAGNI principles, implementation plans embed these core development best practices directly into the generated task breakdown. This ensures every granular step with code snippets and file paths produces maintainable, high-quality code without redundancy.

Can I hand off an implementation plan to a subagent for parallel execution?

Yes, implementation plans provide structured execution handoff options. You can execute the plan via subagent-driven development in your current session or run parallel execution in a separate worktree to isolate the feature implementation.

Does implementation planning work for bug fixes as well as new feature specs?

Implementation planning applies to both bug fixes and new feature specifications. It generates structured execution plans with exact file paths, code snippets, test commands, and commit instructions for any multi-step software development task.

Why do I need exact file paths and commit instructions in a dev workflow plan?

Exact file paths and commit instructions in a dev workflow plan eliminate context gaps and ensure consistent code commits. They provide engineers with precise, actionable steps for implementation, preventing inconsistent or poorly tested software.