Plan

This is a Hermes-native plan workflow skill.

Why This Exists

plan exists so a feature or a fix gets its goals, non-goals, risks, acceptance criteria, and verification shape written down and accepted by the user before any code moves, with every step small enough to check and no implementation hidden inside the plan text.

Do Not Use When

• The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
• The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
• The change is risky or architectural and the user wants alternatives compared, a risk review and a recorded decision; use ulw-plan, and keep this skill for the ordinary plan.
• Requirements are too vague to list non-goals or acceptance criteria; use ulw-interview.
• The direction is decided and what is missing is the phase-by-phase refactor shape; use omh-refactor-plan.

Examples

Good example: