plan

Generate a timestamped markdown plan file under .hermes/plans/.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/founderphantom/zola-agent --skill plan-founderphantom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/founderphantom/zola-agent/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/founderphantom/zola-agent --skill plan-founderphantom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode enables Hermes to focus on strategy and documentation by drafting a concrete markdown plan in the active workspace rather than executing tasks.

Core Features & Use Cases

  • Inspect context and constraints to generate a precise plan.
  • Produce a timestamped plan file under .hermes/plans/.
  • Ensure the plan is concrete, testable, and ready for handoff.

Quick Start

Write a concrete markdown plan to .hermes/plans/ with a timestamped filename.

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 workspace automation without executing tasks?

Generate a markdown plan by inspecting context and constraints, then documenting concrete steps without executing tasks. The plan is saved as a timestamped file under .hermes/plans/, ensuring it is testable and ready for handoff within the active workspace.

What is plan mode in a workspace automation workflow?

Plan mode enables strategy and documentation focus by drafting a concrete markdown plan rather than executing tasks. It inspects context, defines actionable steps, and saves the output to the active workspace for later execution.

How do I create a testable plan file for later handoff in my workspace?

Create a testable plan by inspecting project context, defining concrete steps, and saving the markdown document as a timestamped file under .hermes/plans/. This ensures the generated plan is ready for handoff without executing the tasks.

Can I use planning mode to inspect context before modifying my active workspace?

Yes, planning mode inspects context and constraints to generate a precise plan without modifying your active workspace. It outputs a timestamped markdown file under .hermes/plans/ for review before any execution occurs.

Why does my workspace need a timestamped plan file instead of direct task execution?

A timestamped plan file separates strategy from execution, ensuring the plan is concrete, testable, and ready for handoff. It allows review and modification within the active workspace before any automated tasks are executed.

What's the best way to document automation steps for a later handoff session?

Document automation steps by generating a concrete markdown plan saved as a timestamped file under .hermes/plans/. This approach ensures the plan is testable and ready for handoff without executing the tasks immediately.