Stats
Actions
Tags
From management-portal
Auto-approves web search/fetch and file edit operations; validates structured markdown files (core, competitors, hypotheses, interviews, surveys, MVP plan) after each write/edit to enforce documentation conventions.
2 events · 2 hooks
Safety signals detected in this hook configuration
Where this hook configuration is defined
Defined in hooks/hooks.json
Event handlers and matchers — expand Raw Configuration for the full JSON
mcp__management-portal__(create|update|add|complete|insert|reorder|set|delete|promote|attach|approve|reject|log|start|stop|send|react|edit|resolve|remember)_.*echo '[management-portal] WRITE about to run. Gate 1 (read-after-write): immediately after this, call the matching get_*/list_* tool and confirm the field actually persisted — trust the data effect, not the success string. Gate 3: do not write implementation entities before the task/subtask tree + flow board exist. Never fabricate an id — read it from a list_*/get_* or a create_* response.'mcp__management-portal__(create|update|add|complete|insert|reorder|set|delete|promote|attach|approve|reject|log|start|stop|send|react|edit|resolve|remember)_.*echo '[management-portal] WRITE returned. READ-AFTER-WRITE NOW: call the matching get_*/list_* read tool and confirm the specific field you wrote is present and correct before moving on. A success message is not evidence. The edge of a flow connection may have landed even if the call reported a timeout.'npx claudepluginhub waelfouda/management-portal-plugin --plugin management-portal