skills.rest
rbudiharso
rbudiharsoCOMMUNITY
Explore all skills by this author →
Website𝕏@rbudiharsoGitHub

plan

Writes structured markdown implementation plans to .hermes/plans/ without executing code.

2|Updated Oct 20, 2017
Search Tags:#planning#tdd#documentation#markdown#software development#task breakdown#implementation plan
One-click install
npx skills add https://github.com/rbudiharso/dotfiles --skill plan-rbudiharso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/rbudiharso/dotfiles/tree/main/hermes/.hermes/skills/software-development/plan
Command: npx skills add https://github.com/rbudiharso/dotfiles --skill plan-rbudiharso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns vague feature requests into concrete, step-by-step implementation plans saved as markdown files, so coding work starts from a clear specification instead of guesswork. ## Core Features & Use Cases - Plan-only mode: Inspects the repository with read-only commands and produces a plan without editing project code or running mutating commands. - Structured task breakdown: Enforces bite-sized tasks (2-5 minutes each) with exact file paths, complete code snippets, test commands, and commit steps following TDD, DRY, and YAGNI principles. - Timestamped plan storage: Saves plans under .hermes/plans/ with date-based filenames for traceability. - Use Case: Before implementing a multi-file authentication feature, invoke this skill to generate a task-by-task plan with failing tests, minimal implementations, and verification commands, then hand it off for execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .hermes/plans/ without writing any code.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan before writing code?▼

Invoke the plan skill with your feature request and it inspects the repository read-only, then writes a markdown plan to .hermes/plans/ with goal, approach, bite-sized tasks, exact file paths, code snippets, and verification commands.

What should a good software implementation plan include?▼

A good plan includes the goal, architecture, tech stack, and sequential tasks of 2-5 minutes each. Every task lists exact files to create or modify, complete copy-pasteable code, test commands with expected output, and a commit step.

Does plan mode modify my project files?▼

No. Plan mode only writes the markdown plan file under .hermes/plans/ and uses read-only commands to inspect the repository. It does not edit project code, run mutating commands, commit, or push.

Where are the generated plan files saved?▼

Plans are saved under .hermes/plans/ relative to the active workspace, using a timestamped filename like YYYY-MM-DD_HHMMSS-slug.md. If the runtime specifies a target path, that exact path is used instead.

When should I not use a full implementation plan?▼

Skip detailed planning only for trivial single-step changes. The skill recommends planning even for seemingly simple features, since unstated assumptions are a common source of bugs.

Related Skills

Explore More Software Engineering Skills→
vessuxvessux
1

to-prd

Generate a formal PRD from conversation context and codebase exploration.

Community
Advanced
HanHan666666HanHan666666
10

subagent-driven-development

Delegate each plan task to isolated subagents with two-stage spec and quality reviews.

Community
Advanced
redsub-captainredsub-captain
2

redsub-plan

Generate TDD implementation plans with 2-5 minute tasks and exact file paths.

Community
Intermediate
rkz91rkz91
264

gsd-fast

Execute trivial tasks inline without spawning subagents or planning.

Community
Basic