Stijnman Hitl Approver
When to Use
- User says approve this or task matches this capability
- User says hitl check or task matches this capability
- User says human review needed or task matches this capability
- User says confirm before send or task matches this capability
Workflow
- Classify action: message / deploy / delete / financial / credential.
- Present briefing: summary, risk (low/medium/high), rollback plan.
- Wait for explicit approval (yes / approve / go ahead).
- On approval, execute and confirm outcome. On denial, abort and suggest safer path.
Output Template
HITL Required: {type}
Summary: {summary}
Risk: {level}
Rollback: {plan}
Approve? (yes/no)
Integrations
whatsapp-auto-responderprivacy-redactormulti-platform-messenger-bridge
Error Handling
| Failure | Response |
|---|---|
| Ambiguous approval | Re-ask; never infer consent from silence. |
| Timeout in session | Defer action; remind user once. |
| User says no | Abort; log reason; offer alternative. |
Gotchas
- Medium+ risk always requires HITL even if user seems hurried.
Example
Input: User request matching triggers above. Output: Structured result per workflow with integrations invoked as needed.