writing-plans

Convert project specifications into executable implementation plans with tasks, files, tests, and milestones.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill writing-plans-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/rkz91/coco/tree/main/skills/writing-plans
Command: npx skills add https://github.com/rkz91/coco --skill writing-plans-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a given spec or requirements into a comprehensive, decomposed implementation plan that guides engineers through tasks, files, tests, and milestones.

Core Features & Use Cases

  • Comprehensive planning: outlines tasks, files to touch, tests, docs, and milestones for a project.
  • Task decomposition: breaks work into bite-sized steps with clear ownership and acceptance criteria.
  • Mapping decisions to artifacts: connects design decisions and architecture notes to concrete files and modules.
  • TDD-ready workflow: encourages test-first planning and version-control friendly commits for traceability.

Quick Start

Provide a project spec and I will generate a complete step-by-step implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn project specifications into an executable implementation plan?

Turn project specifications into an executable implementation plan by decomposing requirements into bite-sized tasks, mapping design decisions to specific files, defining testing criteria, and establishing milestones for version control traceability.

What is the best way to decompose multi-step software builds into tasks?

Decompose multi-step software builds by breaking work into bite-sized steps with clear ownership, mapping responsible files and modules, defining acceptance criteria, and establishing documentation requirements for each milestone.

How do I map architecture decisions to concrete files for feature rollouts?

Map architecture decisions to concrete files by generating a comprehensive implementation plan that connects design notes to specific modules, outlines testing criteria, and formats task boundaries for seamless version control commits.

Does this implementation planning approach support a test-first workflow?

This implementation planning approach supports a test-first workflow by encouraging TDD-ready planning, defining testing criteria for each task, and formatting task boundaries for version-control friendly commits to ensure traceability.

Can I use this task decomposition method for complex feature rollouts?

You can use this task decomposition method for complex feature rollouts, as it applies to any multi-step initiative requiring clear task boundaries, responsible file mappings, testing criteria, and milestone tracking.

What should an implementation plan include for software engineering projects?

An implementation plan for software engineering projects should include decomposed bite-sized tasks, responsible file mappings, testing criteria, documentation requirements, and milestones formatted for seamless version control integration.