Defined in hooks/hooks.json
{
"Stop": [
{
"hooks": [
{
"type": "prompt",
"prompt": "# Blueprints Documentation Check\n\nYou are verifying that blueprints/ documentation is current after implementation changes.\n\n## Context\n\n$ARGUMENTS\n\n## Review Checklist\n\n1. **Implementation Changes**: Did you make significant changes (new features, modified architecture, changed APIs, or updated system behavior)?\n\n2. **Documentation Exists**: Does a blueprints/ directory exist in this project?\n\n3. **Documentation Current**: If blueprints/ exists and changes were made, is the relevant documentation up to date?\n\n## Decision Criteria\n\n**Approve** if: No significant implementation changes, OR no blueprints/ directory, OR documentation is current\n**Block** if: Significant changes made AND blueprints/ exists AND documentation is outdated\n\nRespond with JSON: {\"decision\": \"approve\" or \"block\", \"reason\": \"your explanation\"}",
"timeout": 300
}
]
}
],
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "echo '# Blueprint System Available\n\nThis project uses technical blueprints for system documentation.\n\n**MCP Tools:**\n- search_blueprints - Find existing blueprints (use BEFORE creating)\n- read_blueprint - Read current documentation (use BEFORE modifying)\n- write_blueprint - Update documentation (use AFTER implementation)\n\n**When to use:** New features, API changes, architectural modifications, behavior changes.\n\nSee UserPromptSubmit hook for detailed requirements.'"
}
]
}
],
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "han hook reference hooks/ensure-blueprints.md --must-read-first \"blueprints documentation requirements\""
}
]
}
]
}{
"riskFlags": {
"touchesBash": false,
"matchAllTools": false,
"touchesFileWrites": false
},
"typeStats": {
"prompt": 1,
"command": 2
},
"eventStats": {
"Stop": 1,
"SessionStart": 1,
"UserPromptSubmit": 1
},
"originCounts": {
"absolutePaths": 0,
"pluginScripts": 0,
"projectScripts": 0
},
"timeoutStats": {
"commandsWithoutTimeout": 2
}
}