@zack/incident-response-loop
Portable incident-response loop for assess, execute, review, and revision-driven operational follow-through.
Install
agentpm install @zack/incident-response-loop@0.1.0Load
import { loadLoop } from '@agentpm/sdk';
const loop = await loadLoop('@zack/incident-response-loop@0.1.0');Weekly installs
2
0%
Last publish
Today
v0.1.0
Phases
assess
EntryReview the current incident state, identify the active owner and primary risks, and decide whether work should proceed or hand off immediately.
Access intent
Tools: allowedKnowledge: allowedMemory read: allowed
Outcomes
- proceedThe incident has enough context to move into active execution.
- handoffThe incident should be handed off immediately because ownership, authority, or context is insufficient.
execute
Implicit completeCarry out the current operational work, update the working state, and prepare the evidence needed for the next review pass.
Access intent
Tools: allowedKnowledge: allowedMemory read: allowedMemory write: allowed
This phase does not declare explicit outcomes, so it falls through to an implicit
complete outcome.review
Review the current execution result, decide whether the incident can close, whether another execution pass is needed, or whether the work should hand off.
Access intent
Tools: allowedKnowledge: allowedMemory read: allowedMemory write: allowed
Outcomes
- completeThe incident is resolved enough to close the loop cleanly.
- needs-more-workThe current result is incomplete and another execution pass is required.
- handoffThe work should hand off because progress is blocked, ownership changed, or escalation is required.
Transitions
assesson
proceed→executeassesson
handoff→$handoffexecuteon
complete→reviewreviewon
complete→$endreviewon
needs-more-work→executereviewon
handoff→$handoff