plan

Inspect current context and generate a timestamped Markdown plan saved to .hermes/plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/shiftrepo/aws --skill plan-shiftrepo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/shiftrepo/aws/tree/main/HermesAgent/skills/skills/software-development/plan
Command: npx skills add https://github.com/shiftrepo/aws --skill plan-shiftrepo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables planning-only workflows for Hermes, letting you inspect context and craft a detailed markdown plan that is saved to the active workspace without executing any work.

Core Features & Use Cases

  • Plan-only mode: Inspect the current context and produce a concrete, actionable plan without implementing changes.
  • Safe, non-mutating output: Delivers a Markdown plan that can guide subsequent work without altering files or running commands.
  • Plan storage: Saves the generated plan to the active workspace under .hermes/plans/ with a timestamped filename for traceability.
  • Use Case: A product team reviews requirements and creates a step-by-step plan before any code is written.

Quick Start

Generate a concrete plan and save it as a timestamped Markdown file in the active workspace under .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 a markdown plan for feature scoping without writing any code?▼

To generate a markdown plan without writing code, use a planning-only workflow that inspects the current context and produces a concrete, actionable plan. The output is a safe, non-mutating markdown file ready to guide subsequent development work.

What is the best way to save sprint planning documents with traceability?▼

The best way to save sprint planning documents with traceability is to store them as timestamped markdown files. This approach saves the generated plan to the active workspace under a dedicated directory, ensuring non-mutating output and easy historical reference.

Does plan-only mode alter files or execute commands during task planning?▼

Plan-only mode does not alter files or execute commands during task planning. It delivers a safe, non-mutating markdown plan that guides subsequent work, ensuring no changes are made to the active workspace until you explicitly implement the plan.

Can I use workspace automation to create actionable plans for software development?▼

Yes, you can use workspace automation to create actionable plans for software development. By inspecting the current context, the automation produces a structured markdown plan that is concrete, actionable, and ready for handoff before any code is written.

Why should I use a planning-only workflow before implementing features?▼

You should use a planning-only workflow before implementing features to ensure requirements are reviewed and a step-by-step plan is created without mutating files. This approach produces a concrete plan ready for handoff, reducing errors during actual development.