skills.rest
mattniedelman
mattniedelmanCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert high-level specs into structured implementation plans with tasks and file references.

1|Updated Dec 25, 2017
Search Tags:#planning#code review#documentation#implementation#task breakdown#test guidance
One-click install
npx skills add https://github.com/mattniedelman/dotfiles --skill writing-plans-mattniedelman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mattniedelman/dotfiles/tree/main/dot_augment/skills/writing-plans
Command: npx skills add https://github.com/mattniedelman/dotfiles --skill writing-plans-mattniedelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create actionable, step-by-step implementation plans from a clear spec before touching code, ensuring nothing is missed and every task is well defined.

Core Features & Use Cases

  • Structured Plan Templates: Generate a complete plan with a standard header, task breakdown, and file/layout references.
  • Task-Level Guidance: Break tasks into bite-sized steps with code, test, and commit guidance to support TDD and rapid iteration.
  • Use Case: Apply to feature development, refactors, or documentation tasks, turning vague requirements into concrete tasks and milestones.

Quick Start

Use the writing-plans skill to create a plan for implementing a new authentication feature based on a provided spec.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert a high-level spec into a concrete implementation plan?▼

To convert a high-level spec into a concrete implementation plan, generate a structured document with a header, task list, file references, tests, and commit guidance. This ensures nothing is missed and every task is well defined.

What is the best way to break down feature development into actionable tasks?▼

The best way to break down feature development is to generate a structured plan with bite-sized tasks from a clear spec. Each task includes specific code, test, and commit guidance to support test-driven development and rapid iteration.

Can I generate test guidance and commit milestones alongside task breakdowns?▼

Yes, you can generate test guidance and commit milestones alongside task breakdowns. The structured plan format explicitly enforces including test and commit guidance for each task to support test-driven development.

Does this approach work for planning refactors and documentation milestones?▼

Yes, this approach works for planning refactors and documentation milestones. The task-oriented plan format is applicable to general software development workflows, turning vague requirements into concrete milestones.

Do I need a complete spec before starting task breakdown?▼

Yes, you need a clear spec before starting task breakdown. The process converts a high-level spec into actionable steps, ensuring nothing is missed by defining every task well before touching any code.

Related Skills

Explore More Software Engineering Skills→
qq824045252-ship-itqq824045252-ship-it

superpowers-writing-plans

Convert high-level specs into task-by-task implementation plans with file touchpoints.

Community
Advanced
scanadyscanady

tech-writing-plans

Generate step-by-step implementation plans specifying files, code, tests, and commit messages.

Community
Intermediate
ChoiHyunjinChoiHyunjin

subagent-driven-development

Dispatch AI subagents to implement tasks and run two-stage reviews.

Community
Advanced
mcampbellrmcampbellr

gsd-ns-project

Track, create, and audit project milestones with status summaries.

Community
Advanced