plan

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

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill plan-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/software-development/plan
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill plan-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete, actionable implementation plan before touching any code, this Skill produces a detailed markdown plan saved to your workspace, ensuring nothing is implemented prematurely and every step is documented for later execution. ## Core Features & Use Cases - Plan-Only Mode: Inspects the repository with read-only operations and writes a plan file without editing project code, running mutating commands, or committing changes. - Structured Plan Format: Generates plans with goal, architecture, tech stack, bite-sized tasks (2-5 minutes each), exact file paths, complete code snippets, test commands with expected output, and commit steps following TDD, DRY, and YAGNI principles. - Timestamped Storage: Saves plans under .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md relative to the active workspace, working across local, docker, ssh, and other backends. - Use Case: Before building a multi-step feature like user authentication, invoke plan mode to receive a task-by-task breakdown with failing-test-first steps, exact pytest commands, and git commit instructions ready for subagent-driven 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 plan mode with your feature request and the agent inspects the repository read-only, then writes a markdown plan to .hermes/plans/ with goal, architecture, bite-sized tasks, exact file paths, code snippets, and test commands. No project files are modified.

What should a good 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 file paths, complete copy-pasteable code, exact test commands with expected output, and a commit step following TDD.

Where are plan files saved in the workspace?

Plans are saved under .hermes/plans/ with a timestamped filename like YYYY-MM-DD_HHMMSS-slug.md, relative to the active working directory. This path works across local, docker, ssh, modal, and daytona backends.

Does plan mode modify or execute any code?

No, plan mode is strictly read-only for the repository. It never edits project files, runs mutating terminal commands, commits, or pushes. The only file written is the markdown plan itself under .hermes/plans/.

When should I not use plan mode?

Skip plan mode for trivial single-line fixes or when you want immediate execution. Planning adds the most value for multi-step features, complex requirements, or work delegated to subagents where assumptions cause bugs.