plan

Generate a structured markdown plan under .hermes/plans/ without executing code.

Updated May 23, 2026

Search Tags:#workflow #planning #documentation #markdown #plan #feature-development

Ready to run

npx skills add https://github.com/zengbaocheng/hermes-tech-hub --skill plan-zengbaocheng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/zengbaocheng/hermes-tech-hub/tree/main/software-development/plan
Command: npx skills add https://github.com/zengbaocheng/hermes-tech-hub --skill plan-zengbaocheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode generates a concrete, shareable markdown plan stored in .hermes/plans/ rather than executing code.

Core Features & Use Cases

Generate a concrete markdown plan saved under .hermes/plans/ without mutating code.
Provide a structured plan including goals, context, approach, step-by-step plan, affected files, validation, risks, and questions.
Use case: when starting a new feature, run this skill to produce a plan that can be reviewed by teammates before coding.

Quick Start

Create a concrete markdown plan in .hermes/plans/ for the current planning task.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I generate a markdown plan for feature development without executing code?▼

A feature development plan generated without executing code produces a structured markdown file under .hermes/plans/ covering goals, context, approach, steps, affected files, validation, risks, and questions for team review.

What is the best way to create a shareable plan before starting feature development?▼

A shareable feature development plan is a concrete markdown document with defined goals, step-by-step approach, affected files, validation tests, and risks that teammates can review and approve before coding begins.

What sections should a feature development plan include for team review?▼

A feature development plan for team review includes sections for goals, context, approach, step-by-step plan, affected files, validation, risks, and questions, plus a quick-start example reviewers can act on.

Can I use markdown planning for process planning instead of just feature development?▼

Yes, markdown planning supports both feature development and process planning, generating a structured document with goals, steps, tests, and a quick-start example that reviewers can act on.

Does this planning workflow mutate code or only generate documentation?▼

This planning workflow only generates documentation without mutating code, producing a well-structured markdown plan saved under .hermes/plans/ that defines goals, steps, tests, and a quick-start example.