plan

Generate actionable markdown implementation plans saved to .hermes/plans/.

Updated May 5, 2026

Search Tags:#workflow #planning #markdown #implementation roadmap #safe execution #workspace files

Ready to run

npx skills add https://github.com/Z43L/zeus-agent --skill plan-z43l

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Z43L/zeus-agent/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/Z43L/zeus-agent --skill plan-z43l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a user needs progress on a task but wants planning instead of immediate execution, this skill prevents accidental changes by producing an actionable roadmap only.

Core Features & Use Cases

Plan-only workflow: generates a markdown plan without implementing code or performing mutating actions.
Safe, workspace-contained output: saves the plan into the active workspace under .hermes/plans/ with a timestamped filename.
Actionable, verification-ready structure: includes goal, assumptions, step-by-step approach, likely files, tests/validation, and risks/open questions for code-related tasks.

Quick Start

Use the plan skill when you want a task broken into an executable markdown plan and respond with where you want the plan stored in .hermes/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I generate an implementation roadmap without executing code changes?▼

To generate an implementation roadmap without executing code changes, this skill produces an actionable markdown plan with goals, step-by-step approaches, and likely files instead of running mutations. The plan is safely stored in your workspace without altering code.

What is the best way to create a markdown plan for software development tasks?▼

Creating a markdown plan for software development tasks is handled by generating a verification-ready document that includes assumptions, tests, validation steps, and risks. The output is saved automatically as a timestamped file under the `.hermes/plans/` directory.

Can I get a step-by-step workflow plan without modifying my workspace files?▼

Yes, you can get a step-by-step workflow plan without modifying workspace files because this skill enforces plan-only behavior and read-only inspection. It safely defers execution and writes only the markdown plan to disk.

Does this approach support planning for non-code workstreams that require deferred execution?▼

Yes, this approach supports planning for non-code workstreams that require deferred execution. It applies to any scenario where execution must be deferred, producing an actionable roadmap rather than performing mutating actions.

What structure does the generated implementation plan include for validation?▼

The generated implementation plan includes a verification-ready structure containing the goal, assumptions, a step-by-step approach, likely files, tests and validation criteria, and risks or open questions. This ensures the roadmap is fully actionable.

When should I avoid using an automated planning workflow for my project?▼

You should avoid using an automated planning workflow when your project requires immediate code execution rather than a roadmap, because this skill strictly enforces plan-only behavior and intentionally defers all mutating actions.