plan

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

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/i-bebsi/hermes-agent --skill plan-i-bebsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/i-bebsi/hermes-agent/tree/main/hermes-config/skills/software-development/plan
Command: npx skills add https://github.com/i-bebsi/hermes-agent --skill plan-i-bebsi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding a multi-step feature often leads to missed requirements, vague tasks, and rework. This Skill produces a detailed, self-contained implementation plan saved to .hermes/plans/ so that any implementer (human or subagent) can execute it without guessing. ## 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. - Structured task breakdown: Splits work into 2-5 minute tasks with exact file paths, complete copy-pasteable code, exact test commands with expected output, and commit steps following TDD, DRY, and YAGNI principles. - Execution handoff: Saves the plan under .hermes/plans/ with a timestamped filename and offers to execute it via subagent-driven-development with two-stage review. - Use Case: You describe a new authentication feature; the Skill explores the codebase, then saves a plan with sequential tasks covering the User model, password hashing utility, failing tests, verification commands, and commit messages. ## Quick Start Ask the agent to plan the implementation of your feature, for example: plan adding password reset functionality to the user service.

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 plan mode with your feature request and the Skill explores the repository read-only, then writes a markdown plan to .hermes/plans/ with bite-sized tasks, exact file paths, complete code, and verification commands. No project files are modified during planning.

What should a good software implementation plan include?▼

A good plan includes a goal statement, architecture summary, 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.

Where are plan files saved and how are they named?▼

Plans are saved under .hermes/plans/ relative to the active workspace using the pattern YYYY-MM-DD_HHMMSS-<slug>.md. This works across local, docker, ssh, modal, and daytona backends since Hermes file tools are backend-aware.

Can the plan be executed automatically after it is written?▼

Yes, after saving the plan the Skill offers execution via the subagent-driven-development skill. Each task is dispatched to a fresh subagent with full context, followed by spec compliance review and code quality review before proceeding.

When should I not use plan mode?▼

Plan mode is unnecessary for trivial single-line fixes or pure questions, since it only produces a document and never implements code. It is designed for multi-step features, complex requirements, and work delegated to subagents.