skills.rest
rickyananda
rickyanandaCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Write implementation plans with exact files, tests, and commit steps.

1|Updated May 18, 2026
Search Tags:#planning#tdd#documentation#implementation#subagents#task-breakdown
One-click install
npx skills add https://github.com/rickyananda/hermes-skills --skill writing-plans-rickyananda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/rickyananda/hermes-skills/tree/main/software-development/writing-plans
Command: npx skills add https://github.com/rickyananda/hermes-skills --skill writing-plans-rickyananda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature request or messy idea into a clear implementation plan that a developer can execute without guessing.

Core Features & Use Cases

It breaks work into bite-sized tasks, specifies exact files and changes, and includes test commands, verification steps, and commit guidance. It is useful for planning multi-step features, coordinating subagent execution, and documenting complex software changes before implementation. It helps teams and individual developers avoid vague requirements, missed edge cases, and inconsistent handoffs.

Quick Start

Ask the AI to create an implementation plan for your feature request with exact file paths, step-by-step tasks, tests, and verification notes.

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 for a multi-step software feature?▼

To create an implementation plan, break feature requirements into small executable tasks with exact file paths, specific tests, and sequential commit steps. This ensures developers can execute the work without guessing or missing edge cases.

How do I write clear handoff instructions for delegating codebase exploration tasks?▼

Writing clear handoff instructions requires specifying exact files, complete code examples, precise verification commands, and sequential task ordering to make the delegated implementation obvious for subagents or other developers.

What is the best way to break down requirements into executable tasks with TDD documentation?▼

Breaking down requirements with TDD documentation involves splitting work into bite-sized tasks that specify exact file changes, include test commands, outline verification steps, and provide commit guidance for each sequential change.

Can I use implementation plans to coordinate subagent execution for complex codebase changes?▼

Yes, implementation plans coordinate subagent execution by providing clear handoff instructions with exact file paths, complete code examples, and precise verification commands, making complex software changes obvious to execute.

When do I need to write an implementation plan before starting feature work?▼

You need an implementation plan when facing multi-step feature work, messy feature requests, or complex software changes. It prevents vague requirements, missed edge cases, and inconsistent handoffs by documenting exact files and tests beforehand.

Related Skills

Explore More Software Engineering Skills→
Pear-CommercePear-Commerce

gsd-research-phase

Researches implementation approaches for a GSD project phase and outputs structured documentation.

Official
Advanced
UniClipboardUniClipboard
1.5k

executing-plans

Execute plans sequentially with mandatory verification and code-review checkpoints.

Official
Advanced
ZardLi1115ZardLi1115
4

writing-plans

Generate implementation plans with TDD tasks and exact file paths.

Community
Intermediate
samjhechtsamjhecht
4

writing-plans

Generate task-level implementation plans with exact file paths and code samples.

Community
Basic