writing-plans
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.
npx skills add a5c-ai/babysitter --skill writing-plans --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- 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`
- Task Structure
- Plan Format
- Execution Handoff
- Agents Used
- Tool Use
What does the writing-plans skill do?
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.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill writing-plans --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.