The structured plan before your next big process rollout. Who does what, where to stop, how to roll back.
A Hermes Agent skill for creating structured non-code process plans — business workflows, automation setups, data migrations, product launches, and operational rollouts.
When you ask your agent to plan a process, Smartplan ensures the plan includes:
- Context & prerequisites — what exists, what's needed, what's assumed
- Sequenced execution steps — each with a named responsible, a concrete action, a deliverable, and an executable verification
- GO gates — explicit human validation points before any external mutation
- Rollback — 3 levels (immediate cancel, restore from backup, full rollback) with observable triggers
- Final verification — independently checkable completion criteria + proof of success
Most agent planning skills are code-oriented (TDD, file paths, git commits). There was no structured skill for business process deployment — the kind of plan where you need "who does what, in what order, with what GO gates, and how to roll back if it breaks."
Smartplan fills that gap.
/learn https://github.com/Kavyrocom/smartplan
That's it. Hermes Agent fetches the repo and installs the skill automatically.
Copy the smartplan folder into your Hermes skills directory:
~/.hermes/skills/productivity/smartplan/
├── SKILL.md
├── templates/
│ └── plan-template.md
└── references/
└── example-plan.md
Your agent should be able to load the skill:
skill_view(name='smartplan')
1. Slash command (fastest)
Once installed, every skill is automatically a slash command in Hermes. Just type:
/smartplan
Then describe your process. The skill loads and waits for your input.
You can also pass the task directly:
/smartplan Plan the deployment of our post-purchase survey: webhook, storage, Slack notification.
2. Natural language
Just ask your agent to plan something — the skill auto-loads when it matches:
"Plan the deployment of our post-purchase survey: webhook, storage, Slack notification."
"Create a deployment plan for migrating our CRM data to the new system."
"I need a rollout plan for our new onboarding automation."
The agent will:
- Load this skill
- Inspect the context (read-only)
- Produce a structured plan saved to
.hermes/plans/ - List the GO gates and offer execution — but not execute without your explicit go-ahead
- Code implementation plans → use
software-delivery-workfloworsuperpowers:writing-plans - Recurring automated routines → use a cronjob
- Simple 2-3 action tasks → just do it, no plan needed
Every plan produced by Smartplan follows the same structure:
Header (objective, scope, owner, date, status)
1. Context & prerequisites
2. Execution steps (responsible + action + deliverable + verification + risk)
3. GO gates (gate / after step / condition / who validates)
4. Rollback (3 levels + observable triggers)
5. Final verification (completion criteria + proof of success)
6. Risks (optional)
7. Notes (optional)
MIT
David Schkiwisk — kavyro.com