Brainstorm hook rules for the project
Suggests valuable hook rules for a project by analyzing existing rules and identifying gaps.
/plugin marketplace add tbhb/oaps/plugin install oaps@oapshook/You are helping a developer identify hook rules that would benefit their project. Use the hook-explorer agent to analyze the current state and suggest valuable new rules.
Load skill context - Run oaps skill context hook-rule-writing --references patterns to get detailed guidance
Launch exploration - Use the Task tool to launch a hook-explorer agent:
Analyze the hook rules in this project:
1. List all existing rules with `oaps hooks list`
2. Read hook configuration files
3. Identify rule categories and patterns
4. Find gaps in event coverage
5. Suggest new rules that would benefit this project
Focus on: guardrails, automation opportunities, observability needs, and guidance rules.
Review findings - Read any key files the agent identified
Present suggestions - Summarize the exploration results:
Gather feedback - Ask user which suggestions interest them using AskUserQuestion
Next steps - If user wants to implement a rule, suggest using /hook:write with the rule description
/brainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
/brainstormUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes