The four plan lifecycle events on the framework event bus and how to subscribe with `manage-automations` instead of bespoke integration code. Use when a user wants to be notified or trigger work on plan creation, comments, publishes, or status changes.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add BuilderIO/agent-native --skill plan-events --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plan Events?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/builderio-plan-events)More formats (shields.io, HTML) on the badges page.
---
name: plan-events
description: >-
The four plan lifecycle events on the framework event bus and how to subscribe
with `manage-automations` instead of bespoke integration code. Use when a user
wants to be notified or trigger work on plan creation, comments, publishes, or
status changes.
---
# Plan Events
The plan app emits four events on the framework event bus: `plan.created`,
`plan.commented`, `plan.published`, and `plan.status.changed`. Automations can
subscribe to any of them — if a user asks to "notify me when someone comments"
or similar, call `manage-automations` with `action=define` (trigger `plan.commented`,
optional condition on `resolutionTarget`) rather than writing bespoke integration
code. See the `automations` skill and the [Visual Plans events docs](/docs/template-plan#events)
for payload schemas and recipe examples.
## Related Skills
- **plan-comments-and-feedback** — the comment data an automation reacts to.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...