writing-plans

Converts vague specifications into detailed step-by-step implementation plans.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/programadorisgod/builder-projects --skill writing-plans-programadorisgod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/programadorisgod/builder-projects/tree/main/bin/assets/.agents/skills/writing-plans
Command: npx skills add https://github.com/programadorisgod/builder-projects --skill writing-plans-programadorisgod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague specifications into detailed, actionable implementation plans so engineers know exactly what to do.

Core Features & Use Cases

  • Thoroughly outline tasks, files, tests, and commits for each feature.
  • Provide a repeatable plan template that saves to docs/plans.
  • Supports worktree-based brainstorming and incremental plan refinement.

Quick Start

Outline the feature tasks in bite-sized steps and save the plan to docs/plans/YYYY-MM-DD-writing-plans.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn vague specs into step-by-step implementation plans?

You create an implementation plan by outlining bite-sized feature tasks, required files, tests, and commits, then saving the structured plan to the docs/plans directory using a date-based naming convention.

What is the best way to document engineering tasks for upfront planning?

Documenting engineering tasks for upfront planning involves using structured plan templates with frontmatter metadata to thoroughly outline task details, required files, tests, and commits for incremental project refinement.

Can I use worktree-based brainstorming to refine task templates?

Yes, worktree-based brainstorming supports incremental plan refinement, allowing you to iteratively develop and adjust structured task templates before finalizing the implementation documentation for your engineering project.

Does this planning approach work for different project sizes?

Yes, this planning approach is applicable to engineering tasks requiring thorough upfront planning across different project sizes, converting ambiguous specifications into actionable steps regardless of overall scope.

Where should I save implementation plans generated from specs?

Implementation plans are saved to the docs/plans directory using a standardized naming convention, specifically formatted as YYYY-MM-DD-writing-plans.md, to maintain consistent documentation organization.