skills.rest
Axeloooo
AxelooooCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Transform feature specifications into test-driven implementation plans with file-level tasks.

Updated Oct 16, 2025
Search Tags:#tdd#documentation#implementation planning#git workflow#task decomposition#test design#spec to code
One-click install
npx skills add https://github.com/Axeloooo/TheDataBay --skill writing-plans-axeloooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Axeloooo/TheDataBay/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/Axeloooo/TheDataBay --skill writing-plans-axeloooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps convert ambiguous or multi-step specs into a clear, buildable roadmap that a developer can execute with minimal context, reducing rework and coordination mistakes.

Core Features & Use Cases

  • Implementation planning from requirements: Produces a task-by-task plan that maps feature scope to concrete file changes and tests.
  • TDD-focused execution guidance: Enforces bite-sized steps that include writing failing tests, implementing minimal code, and verifying outcomes.
  • Repo-aware documentation structure: Directs where plans are saved and how the plan should be organized for clear execution handoff.

Use case: You receive a feature spec for adding a new capability across backend and frontend and need an engineer-friendly plan that identifies exactly what to change and how to test it without guessing.

Quick Start

Use the writing-plans skill to create an implementation plan from your feature requirements before you write any code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn feature specifications into executable implementation plans?▼

Implementation planning from requirements works by decomposing feature specs into bite-sized TDD steps, mapping file-level responsibilities, and defining test/commit checkpoints for clear execution handoff before any code is written.

What is the best way to plan test-driven development for multi-file feature work?▼

Creating a TDD-focused execution plan requires decomposing feature scope into bite-sized steps: write failing tests, implement minimal code, and verify outcomes with exact commands at each commit checkpoint.

Does implementation planning work for features spanning multiple subsystems?▼

Implementation planning applies to multi-step feature work spanning multiple files or subsystems, mapping feature scope to concrete file changes and tests for clear execution handoff across boundaries.

How do I structure implementation plan documentation in my repository?▼

Structure implementation plan documentation by saving plan documents under docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md with YAML frontmatter containing name and description, including concrete code, tests, and exact commands without placeholders.

When should I avoid using a spec-to-code implementation plan?▼

Avoid spec-to-code implementation plans for single-file changes or trivial updates that do not require task decomposition, file-level responsibility mapping, or multi-step test-driven execution checkpoints across subsystems.

Related Skills

Explore More Software Engineering Skills→
yves-syves-s
24

writing-plans

Translate specifications into structured implementation plans with task breakdowns.

Community
Intermediate
hxk622hxk622
8

writing-plans

Generate step-by-step implementation plans with exact file paths and commands.

Community
Intermediate
berlysiaberlysia
9

bugfix

Reproduce bugs, write failing tests, and verify minimal fixes via TDD.

Community
Advanced
idoberkidoberk

writing-plans

Create implementation plans with file mappings, atomic tasks, and review checkpoints.

Community
Advanced