writing-plans

Generate implementation plans with file paths, TDD tasks, and git commands.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/tim-hub/role-based-skills --skill writing-plans-tim-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tim-hub/role-based-skills/tree/main/writing-plans
Command: npx skills add https://github.com/tim-hub/role-based-skills --skill writing-plans-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides fully detailed, step-by-step implementation plans for engineers who join a project with zero codebase context, removing ambiguity about what to change, how to test it, and how to commit it.

Core Features & Use Cases

  • Bite-sized TDD tasks: Breaks work into 2-5 minute actions like writing a failing test, implementing the minimal code, running tests, and committing.
  • Exact file-level guidance: Lists precise file paths to create or modify, full code examples, test locations, and exact git commands.
  • Execution handoff: Produces a standardized markdown plan saved under docs/plans with an offer for subagent-driven or parallel execution.

Quick Start

Ask the assistant to "Create an implementation plan named [Feature Name] that includes a header, architecture, tech stack, and bite-sized TDD tasks and save it to docs/plans/YYYY-MM-DD-[feature-name].md".

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan with exact file paths and TDD steps?

You can generate a comprehensive implementation plan with exact file-level modifications, full code examples, and TDD-style task steps by providing a completed design to produce bite-sized 2-5 minute testing and coding actions.

What are bite-sized TDD tasks for engineers joining a project with no context?

Bite-sized TDD tasks are 2-5 minute actions like writing a failing test, implementing minimal code, running tests, and committing, specifically designed to remove ambiguity for engineers lacking prior codebase context.

How do I break down a completed software design for developer handoff?

Breaking down a completed software design for handoff involves generating explicit file-level modifications, runnable test snippets, exact git commit commands, and a standardized markdown plan saved under a structured docs directory.

Can I generate exact git commit commands and test snippets alongside an implementation plan?

Yes, generating an implementation plan includes producing exact git commit commands, runnable test snippets, and full code examples to ensure engineers can execute file-level modifications step by step without ambiguity.

Does this approach work for backend, frontend, and API implementation plans?

Yes, this approach works for backend, frontend, or API features by producing explicit file-level modifications, TDD-style task steps, and verification instructions regardless of the specific tech stack architecture.