writing-plans

Solid

Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD implementation plans with dependency tracking.

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
54
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Writing Plans ## Overview Create comprehensive implementation plans with bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps, and TDD flow. **Core principle:** Document everything the engineer needs. DRY. YAGNI. TDD. Frequent commits. ## When to Use - After design approval (from brainstorming) - When you have specs/requirements for multi-step work - Before any implementation begins ## Task Structure Each task follows: Write failing test -> Verify fail -> Implement minimal code -> Verify pass -> Commit ## Plan Format - Header: Goal, Architecture, Tech Stack - Tasks with exact file paths and complete code - TDD steps with expected output - Task persistence via `.tasks.json` ## Execution Handoff After plan is written, choose: 1. **Subagent-Driven** - Fresh agent per task with two-stage review 2. **Batch Execution** - Execute in batches with human checkpoints ## Agents Used - Process agents defined in `writing-plans.js` ## Tool Use Invoke via babysitter process: `methodologies/superpowers/writing-plans`

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Related Skills