8b6beaab5f
* docs(audit): correctness pass across getting-started, reference, features, messaging, developer-guide, guides, integrations, user-guide * docs: add PR coverage for last 30d + Nous Portal weave + nav reorg + build fixes - Add docs for top user-visible PRs that shipped without docs (api-server session control, kanban features, telegram pin/edit, provider client tag, xAI retired-model migration, cron name lookup, --branch update flag, etc.) - Apply Nous Portal weave across 23 pages (tasteful one-liners on getting-started/learning-path, configuration, overview, vision, x-search, credential-pools, provider-routing, cron, codex-runtime, profiles, docker, messaging/index, multiple guides, plus FAQ + index promotion) - Reorganize sidebar: split Messaging into Popular/M365/Chinese/Other, Reference into Command/Configuration/Tools-Skills sub-categories, add orphan developer-guide pages (web-search-provider-plugin, browser-supervisor), move features from Integrations back to Features, fold lone spotify into Media & Web. - Regenerate skill stubs + catalogs (kanban-codex-lane, hermes-s6-container- supervision, web-pentest) - Fix broken anchor links (security/cron, configuration/fallback, telegram large-files, adding-platform-adapters step-by-step)
77 lines
2.7 KiB
Markdown
77 lines
2.7 KiB
Markdown
---
|
|
title: "Plan — Plan mode: write markdown plan to"
|
|
sidebar_label: "Plan"
|
|
description: "Plan mode: write markdown plan to"
|
|
---
|
|
|
|
{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
|
|
|
|
# Plan
|
|
|
|
Plan mode: write markdown plan to .hermes/plans/, no exec.
|
|
|
|
## Skill metadata
|
|
|
|
| | |
|
|
|---|---|
|
|
| Source | Bundled (installed by default) |
|
|
| Path | `skills/software-development/plan` |
|
|
| Version | `1.0.0` |
|
|
| Author | Hermes Agent |
|
|
| License | MIT |
|
|
| Platforms | linux, macos, windows |
|
|
| Tags | `planning`, `plan-mode`, `implementation`, `workflow` |
|
|
| Related skills | [`writing-plans`](/docs/user-guide/skills/bundled/software-development/software-development-writing-plans), [`subagent-driven-development`](/docs/user-guide/skills/bundled/software-development/software-development-subagent-driven-development) |
|
|
|
|
## Reference: full SKILL.md
|
|
|
|
:::info
|
|
The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
|
|
:::
|
|
|
|
# Plan Mode
|
|
|
|
Use this skill when the user wants a plan instead of execution.
|
|
|
|
## Core behavior
|
|
|
|
For this turn, you are planning only.
|
|
|
|
- Do not implement code.
|
|
- Do not edit project files except the plan markdown file.
|
|
- Do not run mutating terminal commands, commit, push, or perform external actions.
|
|
- You may inspect the repo or other context with read-only commands/tools when needed.
|
|
- Your deliverable is a markdown plan saved inside the active workspace under `.hermes/plans/`.
|
|
|
|
## Output requirements
|
|
|
|
Write a markdown plan that is concrete and actionable.
|
|
|
|
Include, when relevant:
|
|
- Goal
|
|
- Current context / assumptions
|
|
- Proposed approach
|
|
- Step-by-step plan
|
|
- Files likely to change
|
|
- Tests / validation
|
|
- Risks, tradeoffs, and open questions
|
|
|
|
If the task is code-related, include exact file paths, likely test targets, and verification steps.
|
|
|
|
## Save location
|
|
|
|
Save the plan with `write_file` under:
|
|
- `.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md`
|
|
|
|
Treat that as relative to the active working directory / backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.
|
|
|
|
If the runtime provides a specific target path, use that exact path.
|
|
If not, create a sensible timestamped filename yourself under `.hermes/plans/`.
|
|
|
|
## Interaction style
|
|
|
|
- If the request is clear enough, write the plan directly.
|
|
- If no explicit instruction accompanies `/plan`, infer the task from the current conversation context.
|
|
- If it is genuinely underspecified, ask a brief clarifying question instead of guessing.
|
|
- After saving the plan, reply briefly with what you planned and the saved path.
|