plan

Create markdown implementation plans with goals, file changes, tests, and risks.

Updated May 9, 2026

Search Tags:#workflow #planning #markdown #software development #implementation #repository

Ready to run

npx skills add https://github.com/pmcdowall/hermes-skills --skill plan-pmcdowall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/pmcdowall/hermes-skills/tree/main/software-development/plan
Command: npx skills add https://github.com/pmcdowall/hermes-skills --skill plan-pmcdowall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users avoid premature implementation by turning software tasks into structured markdown plans before any code changes are made.

Core Features & Use Cases

Planning Workflow: Creates actionable implementation plans with goals, context, approaches, file changes, tests, risks, and open questions.
Safe Execution Boundaries: Keeps the session in planning mode by preventing code edits, mutating commands, commits, pushes, and external actions.
Use Case: When preparing a feature change in a repository, use this Skill to produce a detailed plan that identifies affected files and validation steps before development begins.

Quick Start

Use the plan skill to create a detailed implementation plan for the current software development task.

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 before coding in a software repository?▼

An implementation plan provides a structured markdown document outlining development goals, context, and approaches before coding. It details expected file changes, necessary tests, potential risks, and open questions to guide repository changes safely.

What is the best way to analyze file impact and risks for a new software feature?▼

Impact and risk analysis is performed by generating a structured markdown plan that identifies affected repository files and validation steps. This planning process highlights development risks and open questions without executing mutating operations.

Can I use a planning workflow to prevent premature code edits in my repository?▼

Yes, a planning workflow prevents premature code edits by enforcing safe execution boundaries. It keeps the development session in planning mode, blocking code edits, mutating commands, commits, pushes, and external actions until the markdown plan is complete.

How do I structure development goals and validation steps for a repository change?▼

Structure development goals and validation steps by generating a markdown implementation plan. This document captures the required software development context, approach, file changes, tests, and risk assessment to validate the repository update before execution.

Does the markdown planning process execute any mutating commands or git pushes?▼

No, the markdown planning process does not execute mutating commands, git pushes, or external actions. It strictly operates in planning mode to generate plan documents in a designated workspace location without performing any code changes.