plan

Creates timestamped, executable markdown plans in .hermes/plans/ without mutating the repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode creates a concrete, executable markdown plan that guides projects without mutating the repository.

Core Features & Use Cases

  • Generates structured markdown plans with goals, context, approach, step-by-step tasks, changes to expect, tests, and risk assessment.
  • Saves plans to a timestamped file under the designated workspace (.hermes/plans/) for reproducibility and auditing.
  • Applicable to software development, product planning, and operational workflows requiring a clear blueprint before action.

Quick Start

Create a timestamped plan by providing a task, and the system will save the markdown plan to .hermes/plans/YYYY-MM-DD_HHMMSS-plan.md

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an actionable markdown plan for a software development workflow?

To create a markdown plan, provide your task details and the system generates a structured document outlining goals, approach, step-by-step tasks, tests, and risks. It saves this executable blueprint without mutating your repository.

What is the best way to document project planning steps before making code changes?

The best way to document project planning is generating a timestamped markdown file under a designated workspace. This approach enforces a clear outline of context, goals, validation, and risks before any repository mutation occurs.

Does this planning approach save files directly in the repository root?

No, this planning approach does not save files in the repository root. It enforces a strict save location under a designated workspace directory, using timestamped filenames to ensure reproducibility and auditing without altering source code.

Can I use this structured planning mode for operational workflows outside of software development?

Yes, you can use this structured planning mode for operational workflows. It is applicable to product planning and any operational process requiring a step-by-step blueprint with goals, approach, validation, and risk assessment.

What specific sections are included in the generated markdown plan?

The generated markdown plan includes specific sections for goals, context, approach, step-by-step tasks, expected changes, tests, risk assessment, and questions. This structure ensures a comprehensive blueprint for project execution.