skill package

Plan

Plan mode — write markdown plan without executing.

StrategyVerifiedv1.0.0publicAdmin

100% eval4.9 rating3,944 installs3 targets

Edit in Build

Permissions, source, and what this skill claims to do.

Contract

What this skill may access, and where it can install.

read_fileslow risk

Analyze workspace context.

networkmedium risk

Access external AI resources.

Compatibility

AntigravityClaudeCodex

Source

README and SKILL.md for the current version.

README

# plan Plan mode — write markdown plan without executing.

SKILL.md

---
name: plan
description: Plan mode — write markdown plan without executing.
---

# Plan

## Description
Write a concrete, actionable markdown plan before any implementation. No code, no mutations — just planning. The plan goes in `.hermes/plans/` and serves as the single source of truth for what will be built and how.

## When to use
- When the user says "plan this" or asks for a design first.
- Before starting any non-trivial implementation (specs, architecture, new features).
- When the user wants to review and approve before work begins.

## Instructions
- Do not implement code. Do not edit project files except the plan file.
- Do not run mutating commands, commit, or push.
- You may inspect the repo with read-only commands to gather context.

### Plan Structure
A complete plan includes:
- **Goal**: single sentence, what we're building.
- **Current context**: what exists today, what assumptions we're making.
- **Proposed approach**: the strategy, architectural decisions, tradeoffs.
- **Step-by-step plan**: numbered, actionable steps in execution order.
- **Files likely to change**: exact paths for creation/modification.
- **Tests / validation**: how each step will be verified.
- **Risks, tradeoffs, open questions**: what's uncertain, what could go wrong.

### Save Location
Save as `.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md`
Use a descriptive slug based on the feature name.

### Interaction Style
- If the request is clear enough, write the plan directly.
- If genuinely underspecified, ask a brief clarifying question.
- After saving, reply with what you planned and the saved path.

## Examples
**Input:** "Plan the implementation of user authentication"
**Output:** A markdown plan saved to `.hermes/plans/2026-06-01_143000-user-auth.md` with goal, current auth setup, approach (JWT + bcrypt), 6 implementation steps, file paths for each, test strategy per step, and risks (token refresh, password reset).

**Input:** "Plan the migration from REST to GraphQL"
**Output:** Plan covering migration strategy (strangler fig), schema design, resolver patterns, auth integration, client updates, rollback plan, and a phased rollout with validation gates at each phase.

Reception

Community feedback for this skill.

No reviews yet.

Loading studio…

--- name: plan description: Plan mode — write markdown plan without executing. --- # Plan ## Description Write a concrete, actionable markdown plan before any implementation. No code, no mutations — just planning. The plan goes in `.hermes/plans/` and serves as the single source of truth for what will be built and how. ## When to use - When the user says "plan this" or asks for a design first. - Before starting any non-trivial implementation (specs, architecture, new features). - When the user wants to review and approve before work begins. ## Instructions - Do not implement code. Do not edit project files except the plan file. - Do not run mutating commands, commit, or push. - You may inspect the repo with read-only commands to gather context. ### Plan Structure A complete plan includes: - **Goal**: single sentence, what we're building. - **Current context**: what exists today, what assumptions we're making. - **Proposed approach**: the strategy, architectural decisions, tradeoffs. - **Step-by-step plan**: numbered, actionable steps in execution order. - **Files likely to change**: exact paths for creation/modification. - **Tests / validation**: how each step will be verified. - **Risks, tradeoffs, open questions**: what's uncertain, what could go wrong. ### Save Location Save as `.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md` Use a descriptive slug based on the feature name. ### Interaction Style - If the request is clear enough, write the plan directly. - If genuinely underspecified, ask a brief clarifying question. - After saving, reply with what you planned and the saved path. ## Examples **Input:** "Plan the implementation of user authentication" **Output:** A markdown plan saved to `.hermes/plans/2026-06-01_143000-user-auth.md` with goal, current auth setup, approach (JWT + bcrypt), 6 implementation steps, file paths for each, test strategy per step, and risks (token refresh, password reset). **Input:** "Plan the migration from REST to GraphQL" **Output:** Plan covering migration strategy (strangler fig), schema design, resolver patterns, auth integration, client updates, rollback plan, and a phased rollout with validation gates at each phase.