Skip to content

a5c-ai/babysitter / library/methodologies/superpowers/skills/writing-plans

writing-plans

Verified

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.

FileKindSize
README.mdmarkdown457 B
SKILL.mdskill md1.2 KB
---
name: writing-plans
description: 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.
graph:
  domains: [domain:software-engineering]
  skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:tech-lead, role:backend-engineer]
---

- 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`
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall