writing-plans

Generate implementation plans with tracked MCP issues and verification steps.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/bacchus-labs/wrangler --skill writing-plans-bacchus-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/bacchus-labs/wrangler/tree/main/skills/writing-plans
Command: npx skills add https://github.com/bacchus-labs/wrangler --skill writing-plans-bacchus-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, actionable implementation plans from specifications, ensuring clarity and completeness for developers.

Core Features & Use Cases

  • Task Breakdown: Decomposes specifications into bite-sized, manageable tasks.
  • MCP Issue Generation: Creates tracked issues with exact file paths, code examples, and verification steps.
  • Plan File Creation: Optionally generates an architecture overview for complex implementations.
  • Use Case: After a product specification is finalized, use this Skill to generate all the necessary development tasks, including code snippets and testing instructions, ready for the engineering team to execute.

Quick Start

Use the writing-plans skill to create detailed implementation tasks for the specification located at 'specs/new-feature.md'.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from a specification?

To generate an implementation plan, provide a finalized product specification to the Skill. It decomposes the specification into bite-sized, manageable tasks, creating tracked MCP issues with exact file paths, complete code examples, and verification steps.

Can I create tracked MCP issues with exact file paths and code examples automatically?

Yes, you can create tracked MCP issues automatically. The Skill generates issues containing exact file paths, complete code examples, and verification steps directly from your specification to guide developers.

What is the best way to break down specifications into bite-sized developer tasks?

The best way to break down specifications into bite-sized developer tasks is using automated task decomposition. This process transforms broad specifications into actionable items, ensuring clear developer guidance with exact code examples and verification steps.

Does this task breakdown process generate an architecture overview plan file?

Yes, the task breakdown process optionally generates a plan file. This architecture overview provides a high-level summary for complex implementations alongside the detailed, bite-sized tasks and tracked MCP issues.

Do I need a finalized product specification before generating development tasks?

Yes, you need a finalized product specification before generating development tasks. The Skill requires a defined specification to accurately decompose requirements into actionable tasks with complete code examples and testing instructions.

Why should I use systematic task decomposition for software development workflows?

Systematic task decomposition addresses the need for clear developer guidance in software development workflows. It ensures clarity and completeness by breaking specifications into manageable tasks with exact file paths and verification steps.