skills.rest
jordanhindo
jordanhindoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate end-to-end implementation plans with TDD tasks and file paths.

4|1|Updated Jan 22, 2026
Search Tags:#tdd#implementation planning#task decomposition#docs#file paths#engineering workflow#test planning
One-click install
npx skills add https://github.com/jordanhindo/Turtlez --skill writing-plans-jordanhindo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jordanhindo/Turtlez/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/jordanhindo/Turtlez --skill writing-plans-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

writing-plans helps you translate a feature idea or requirements into an actionable implementation plan that a developer can follow even with zero knowledge of the codebase.

Core Features & Use Cases

  • Spec-to-plan creation: Converts requirements into a complete task breakdown with file touch points, testing steps, and commit instructions.
  • Bite-sized, TDD-oriented workflow: Structures work so each step is small (typically 2–5 minutes) and includes “write failing test → verify fail → minimal implementation → verify pass → commit.”
  • Execution-ready plan artifacts: Saves plans to a date-stamped docs path so they can be executed consistently in later sessions.

Example use case: you receive a new feature spec for an RLM component change and need a clear plan that identifies exactly which files to modify and how to prove correctness with tests.

Quick Start

Use this skill when you have a spec for a multi-step task and want an implementation plan saved to docs/plans/ with a TDD, file-accurate checklist of what to test and implement.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a feature spec into a step-by-step implementation plan?▼

Implementation planning converts a feature spec into a step-by-step build plan by decomposing work into bite-sized, test-driven tasks with exact file paths and commands. It generates a task breakdown that developers can follow with zero prior codebase knowledge.

What is TDD-oriented task decomposition for multi-step engineering changes?▼

TDD task decomposition breaks multi-step engineering changes into small iterations, typically 2-5 minutes each. Every task follows a strict sequence: write a failing test, verify the failure, write minimal implementation code, verify the pass, and commit.

How do I create test-driven development plans with specific file paths and commands?▼

Test-driven development plans are generated by mapping exact file touch points and testing steps from a spec. The plan enforces deterministic execution by specifying exactly which files to modify and which commands to run to prove correctness.

Does implementation planning work for navigating unfamiliar codebases during feature development?▼

Implementation planning works for unfamiliar codebases by providing a guided path through codebase navigation, testing, and documentation updates. The generated plan identifies exact file modifications so an engineer can execute multi-step changes without prior knowledge.

Where are generated implementation plan artifacts saved for consistent execution?▼

Implementation plan artifacts are saved to a date-stamped path at docs/plans/YYYY-MM-DD-feature-name.md. This ensures plans can be executed consistently across later sessions using a structured plan document header.

What's the best way to structure engineering workflow plans for continuous execution?▼

Engineering workflow plans are structured by saving date-stamped markdown documents with YAML frontmatter headers. This deterministic format allows tasks to be executed consistently in later sessions by providing file-accurate checklists for testing and implementation.

Related Skills

Explore More Software Engineering Skills→
devMoezdevMoez
1

writing-plans

Generate repository-aware implementation plans with test-driven steps.

Community
Intermediate
quiznatquiznat

writing-plans

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

Community
Advanced
Marwan78888Marwan78888
16

writing-plans

Generate implementation plans with task breakdowns and file mappings from specs.

Community
Advanced
malue-aimalue-ai
36

planning-task

Generate structured task plans with dependencies in plan.json and todo.md.

Official
Intermediate