plan

Writes actionable markdown implementation plans with bite-sized tasks, exact file paths, and complete code.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/decniner/HermesP1 --skill plan-decniner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/decniner/HermesP1/tree/main/.hermes-backup/skills/software-development/plan
Command: npx skills add https://github.com/decniner/HermesP1 --skill plan-decniner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature request into working code often fails because the plan is vague, tasks are too large, or file paths and code are missing. This Skill produces a concrete, step-by-step implementation plan saved to .hermes/plans/ so execution becomes mechanical and reviewable. ## Core Features & Use Cases - Plan-only mode: Inspects the repository with read-only commands and writes a markdown plan without modifying project code or running mutating commands. - Bite-sized task breakdown: Splits work into 2-5 minute tasks, each with exact file paths, complete copy-pasteable code, exact test commands with expected output, and commit steps. - TDD and engineering discipline: Applies DRY, YAGNI, test-driven development, and frequent commits throughout the plan structure. - Use Case: Ask for a plan to add user authentication, and receive a timestamped markdown file under .hermes/plans/ containing sequential tasks from model creation through password hashing, each with failing tests, minimal implementations, and verification commands. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to the workspace plans directory 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 write a good software implementation plan before coding?▼

Break the feature into 2-5 minute tasks, each with exact file paths, complete copy-pasteable code, exact test commands with expected output, and a commit step. Follow a TDD cycle per task: write the failing test, verify it fails, implement minimally, verify it passes, then commit.

How to plan a feature without modifying any project code?▼

Use plan mode, which restricts the agent to read-only repository inspection and writes only a markdown plan file. The plan is saved under .hermes/plans/ with a timestamped filename, and no mutating commands, commits, or file edits are performed.

Where are the generated implementation plans 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 provides a specific target path, that exact path is used instead.

What makes an implementation plan task too big?▼

A task is too big when it spans multiple files or more than about 5 minutes of work, such as building an entire authentication system in one step. Split it into single-action steps like creating one model, adding one field, or writing one utility function.

When should I skip writing a full implementation plan?▼

The skill recommends almost never skipping it, since even simple features hide assumptions that cause bugs. It is especially required before multi-step features, complex requirement breakdowns, and delegation to subagents for task-by-task execution.