---
name: planning
description: "Write actionable, bite-sized implementation plans before coding — merged from plan + writing-plans."
version: 1.0.0
---

# Planning

When the user asks you to plan before implementing, produce a structured markdown plan.

## Format

```markdown
# Plan: <Brief Title>

## Steps
1. **Step description** — detail (file paths, key decisions)
2. ...
3. ...

## Files to modify
- path/to/file.ext — what changes

## Risks
- anything to watch out for

## Verification
- how to confirm the work is correct
```

## Rules

- Prefer bite-sized, independently testable steps over a single giant plan
- Each step should have a clear "done" signal (builds, passes test, visible change)
- Flag blocking dependencies explicitly
- Estimate complexity: Easy, Moderate, Difficult
- Keep the plan in `.hermes/plans/<date>-<topic>.md`
- Update the plan as you go — don't let it go stale
- When the plan is approved, execute step by step, not all at once

## References

For full design docs and architecture reference, see the relevant skill in software-development/ or devops/ categories.