plan

Create implementation plans and save them to .hermes/plans/ without modifying files.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill plan-titoprausee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/software-development/plan
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill plan-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you produce a clear implementation plan when you want structure, sequencing, and risk awareness without making any changes to the codebase.

Core Features & Use Cases

  • Planning Only: Focuses the assistant on analysis and planning instead of execution.
  • Workspace-Aware Output: Saves the plan into the active workspace under .hermes/plans/ for easy tracking.
  • Use Case: Use it when a request needs a concrete roadmap for a feature, bug fix, refactor, or workflow change before any files are edited.

Quick Start

Ask the assistant to create a concise plan for the current task and save it in the workspace under .hermes/plans/ without modifying any project files.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan for a feature without modifying project files?

An implementation plan provides a concrete roadmap for features, bug fixes, or refactors without modifying project files. It focuses on analysis and workflow sequencing, saving the output to a workspace directory for review before any execution begins.

What is the best way to document a workflow change before executing it in a repository?

Workflow change documentation captures sequencing and risk awareness for repository tasks. It creates a structured roadmap saved within the workspace, ensuring you can review the planned implementation steps before any code mutations occur.

Can I generate a refactoring roadmap for my codebase without actually changing the code?

Yes, you can generate a refactoring roadmap that strictly avoids code changes. The process performs read-only context review and writes the structured plan to a designated workspace folder, deferring all mutating actions until you approve.

How do I inspect a repository to plan a bug fix without triggering unintended mutations?

Repository inspection for bug fix planning operates in a read-only mode to prevent unintended mutations. It analyzes the codebase context and produces a concrete plan file in your workspace, ensuring no executing actions are taken.

Does planning a workflow change require any specific dependencies or environment setup?

Planning a workflow change requires no external dependencies or setup. It operates directly within your current workspace to generate and save the plan document, relying solely on read-only context review.

When should I avoid automatic code execution and use a deferred planning approach instead?

You should use a deferred planning approach instead of automatic code execution when a task requires risk awareness, sequencing, and structure. It ensures changes are deferred until you have reviewed a concrete roadmap saved in your workspace.