skills.rest
GreenyZA
GreenyZACOMMUNITY
Explore all skills by this author →
GitHub

plan

Writes a timestamped markdown implementation plan to .hermes/plans/ without executing code.

Updated Sep 20, 2026
Search Tags:#workflow#planning#tdd#documentation#markdown#implementation plan#plan mode
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill plan-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/GreenyZA/neo-light/tree/main/.hermes-home/skills/software-development/plan
Command: npx skills add https://github.com/GreenyZA/neo-light --skill plan-greenyza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task needs careful thought before any code changes, this Skill enforces a plan-only mode: it produces a concrete, actionable markdown implementation plan saved to the workspace instead of prematurely editing files or running mutating commands. ## Core Features & Use Cases - Plan-only enforcement: Blocks code edits, commits, and mutating terminal commands while allowing read-only repo inspection. - Structured plan authoring: Guides creation of plans with goal, architecture, bite-sized TDD tasks (2-5 minutes each), exact file paths, complete code snippets, and verification commands. - Workspace-aware saving: Stores plans under .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md, compatible with local, docker, ssh, modal, and daytona backends. - Use Case: Before implementing a multi-step feature, invoke plan mode to produce a task-by-task implementation plan with failing-test-first steps and commit points, then hand it off to subagent-driven-development for execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .hermes/plans/ without making any code changes.

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 writes a markdown plan to .hermes/plans/ with a timestamped filename. The plan includes goal, architecture, step-by-step TDD tasks, exact file paths, and verification commands without touching project code.

What should a good implementation plan include?▼

A good plan includes a goal statement, architecture summary, tech stack, and bite-sized tasks of 2-5 minutes each. Every task needs exact file paths, complete copy-pasteable code, exact test commands with expected output, and a commit step.

Can plan mode edit files or run commands?▼

Plan mode only writes the plan markdown file under .hermes/plans/. It permits read-only inspection of the repository but blocks code edits, commits, pushes, and any mutating terminal commands.

Where are plan files saved in the workspace?▼

Plans are saved under .hermes/plans/ with a timestamped slug filename like YYYY-MM-DD_HHMMSS-feature-name.md. The relative path works across local, docker, ssh, modal, and daytona backends.

When should I use plan mode instead of implementing directly?▼

Use plan mode for multi-step features, complex requirement breakdowns, or before delegating to subagents. Even simple-seeming features benefit, since undocumented assumptions are a common source of bugs.

Related Skills

Explore More Software Engineering Skills→
asarchamiasarchami
1

to-specs

Converts requirements and conversation context into structured specification documents.

Community
Intermediate
heidsoftheidsoft

subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code-quality reviews.

Community
Advanced
nachopalmerinachopalmeri

requesting-code-review

Route code changes to a specialized subagent for structured review.

Community
Intermediate
SienkLogicSienkLogic

quick

Execute quick ad-hoc tasks via a towline-executor subagent with PLAN.md and SUMMARY.md artifacts.

Official
Intermediate