skills.rest
cabezno
cabeznoCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Converts requirements into actionable implementation plans with file paths and TDD steps.

Updated May 15, 2026
Search Tags:#tdd#documentation#implementation planning#git workflow#task breakdown#codebase navigation#test commands
One-click install
npx skills add https://github.com/cabezno/bmb-encover-agent --skill writing-plans-cabezno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill writing-plans-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of starting implementation without a clear, file-by-file, test-first plan that accounts for missing context and reduces guesswork.

Core Features & Use Cases

  • Implementation planning from zero context: produces a structured plan that tells an implementer exactly what to read, change, test, and verify.
  • Bite-sized task breakdown with TDD cycles: breaks work into 2–5 minute steps, typically including a full failing-test → minimal code → passing-test loop.
  • Repository-aware execution handoff: guides the workflow using Hermes subagent execution patterns and encourages frequent commits.

Quick Start

Ask the agent to produce a writing implementation plan for your feature, including exact file paths to touch, TDD steps, and commands to run tests and verify behavior.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn software specifications into bite-sized implementation tasks?▼

Implementation planning converts software specifications into actionable tasks with exact file paths, TDD cycles, and verification steps. It breaks work into 2-5 minute steps to reduce guesswork and ensure reliable execution.

What is the best way to plan a multi-step feature refactor without full codebase context?▼

Repository-aware implementation planning generates a structured plan telling an implementer exactly what to read, change, and test. It applies to subagent-driven delegation scenarios where the implementer lacks full codebase context.

How do I break down a feature into TDD cycles for an implementation plan?▼

Break work into 2-5 minute steps using a full failing-test to minimal code to passing-test loop. This enforces TDD practices and deterministic execution handoff for reliable implementation.

Does implementation planning work with git workflow and subagent execution patterns?▼

Implementation planning guides the workflow using Hermes subagent execution patterns and encourages frequent commits. It creates a deterministic execution handoff for reliable implementation across multi-step feature development.

When do I need a file-by-file implementation plan before starting codebase navigation?▼

You need a file-by-file implementation plan when starting implementation without a clear, test-first plan that accounts for missing context. It tells the implementer exactly what to read, change, test, and verify.

Related Skills

Explore More Software Engineering Skills→
sameer-thakkarsameer-thakkar

feature-interview

Conduct structured interviews to gather feature specifications for software planning.

Community
Advanced
CarlosDoersCarlosDoers

planning

Generate implementation plans with file paths, tests, and validation steps.

Community
Advanced
howellshowells
26

detail

Generate implementation plans with file paths, tests, and TDD cycles for /arc:implement.

Community
Advanced
skkeoriwskkeoriw

writing-plans

Write step-by-step implementation plans for software development projects.

Community
Advanced