system-writing-plans

Translates a multi-step specification into a commit-ready, TDD implementation plan with exact file paths, commands, and review checklist.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/luuspoo-create/claude-bildungs-skills --skill system-writing-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-writing-plans
Source: https://github.com/luuspoo-create/claude-bildungs-skills/tree/main/system-writing-plans
Command: npx skills add https://github.com/luuspoo-create/claude-bildungs-skills --skill system-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a multi-step specification or requirements document into a precise, test-first, commit-ready implementation plan that a developer with minimal context can follow.

Core Features & Use Cases

  • File-level mapping: Enumerates which files to create or modify and describes each file's responsibility.
  • TDD task breakdown: Produces bite-sized steps including failing tests, minimal implementations, run commands, expected outputs, and commit instructions.
  • Execution & handoff: Includes plan headers, a self-review checklist, and clear options for subagent-driven or inline execution.
  • Use case: Preparing a new feature for incremental development across multiple subsystems so each commit is small, testable, and reviewable.

Quick Start

Draft a step-by-step implementation plan for the authentication feature and save it to docs/superpowers/plans/2026-04-16-authentication.md.

Frequently Asked Questions about system-writing-plans

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

FAQPage Schema
How do I turn a multi-step specification into a test-driven implementation plan?

A test-driven implementation plan requires translating specifications into file-level mappings, bite-sized TDD task breakdowns with failing tests, exact run commands, and commit instructions for incremental development.

What is file-level mapping in an implementation plan?

File-level mapping enumerates which files to create or modify and describes each file's responsibility, ensuring developers with minimal context understand the exact structural changes needed for the feature.

How do I break down a large feature spec into commit-ready tasks?

Break down large feature specs by producing bite-sized TDD steps including minimal implementations, run commands with expected outputs, and commit instructions, making each task small, testable, and reviewable.

Can I use this approach for onboarding developers with no project context?

Yes, this approach is designed for engineers with little context by providing exact file paths, precise commands, expected outputs, and a self-review checklist to guide incremental development across multiple subsystems.

What's the best way to prepare a specification for incremental development across multiple subsystems?

The best way to prepare a specification for incremental development is generating a detailed plan with failing and passing test code, commit instructions, and a self-review checklist for subagent-driven or inline execution.

Does TDD task decomposition work for features spanning multiple subsystems?

TDD task decomposition works for multi-subsystem features by translating multi-step specifications into atomic, commit-ready tasks with exact file paths and test code, ensuring each commit remains small and testable.