writing-plans

Generate implementation plans with task decomposition and file mapping from project specs.

Updated Feb 11, 2016
One-click install
npx skills add https://github.com/Ehrax/dotfiles --skill writing-plans-ehrax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/writing-plans
Command: npx skills add https://github.com/Ehrax/dotfiles --skill writing-plans-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when you have a spec or requirements for a multi-step task, before touching code. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. Frequent commits.

Core Features & Use Cases

  • Planning for multi-step tasks with clear tasks and milestones
  • Produces self-contained plan documents with files to create or modify, tests, and commit steps
  • Real-world usage: starting from a spec, generate detailed implementation plans that guide engineers.

Quick Start

Provide a project spec to the writing-plans skill to generate a 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 generate an implementation plan from a project spec?▼

To generate an implementation plan from a project spec, provide your requirements to trigger multi-step task decomposition, file-structure mapping, and a documented execution path producing a standardized plan document.

What is the best way to break down multi-step engineering tasks before coding?▼

The best way to break down multi-step engineering tasks is generating bite-sized milestones with specific files to modify, testing requirements, and frequent commit steps, ensuring a documented execution path for engineers.

How do I map out file structures for software documentation?▼

You can map out file structures for software documentation by processing your project spec to identify which files to create or modify for each bite-sized task, resulting in a self-contained plan document.

Does this planning workflow support version-controlled delivery?▼

Yes, this planning workflow supports version-controlled delivery by producing standardized plan documents with headers, task sections, and frequent commit steps suitable for tracking progress in version control.

Can I use this for decomposing tasks in any software project?▼

Yes, you can use this for decomposing tasks in typical software projects, as it generates self-contained plan documents detailing code, tests, and docs needed for each step regardless of the specific stack.

What do I need to provide to start the task decomposition process?▼

You need to provide a project spec or requirements document to start the task decomposition process, which then outputs a comprehensive implementation plan with defined handoff workflow and milestones.