plan

Generate timestamped Markdown plans saved under .hermes/plans/ without executing code.

Updated May 20, 2026
One-click install
npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill plan-sriramkunamsetty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent/tree/main/hermes-agent/skills/software-development/plan
Command: npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill plan-sriramkunamsetty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability enables stakeholders to produce concrete, review-ready plans in Markdown without running any code or making changes to the repository.

Core Features & Use Cases

  • Plan generation: produce timestamped Markdown plans saved under .hermes/plans/.
  • Plan validation: ensure required sections and milestones are included.
  • Use case: a product team requests a planning document for a sprint with milestones and risk notes.

Quick Start

Write a plan that outlines a 2-week sprint with milestones, risks, and success criteria, and save it to the designated plans folder.

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 project plan without executing any code changes?

To generate a Markdown project plan without side effects, use a planning-only mode that produces a timestamped document with milestones, risks, and deliverables saved to a designated folder.

What is the best way to document sprint milestones and risks before implementation?

Documenting sprint milestones and risks requires generating a review-ready Markdown plan that outlines success criteria and deliverables, ensuring stakeholders align before any implementation begins.

Can I create planning documentation for software development workflows without modifying the repository?

Yes, you can create planning documentation without modifying the repository by running a planning-only process that outputs a concrete Markdown file with no side effects or code execution.

Does the generated Markdown plan include validation for required sections and milestones?

Yes, plan validation ensures the generated Markdown document includes all required sections and milestones, providing a review-ready format for product teams to assess project workflows.

What are the limitations of using a plan-only Markdown generation approach?

The limitation of plan-only Markdown generation is that it strictly produces documentation and does not execute code or make repository changes, requiring a separate process for actual implementation.