h4tcher-capability-discover

> Last updated: 2026-06-06 # Capability Discover (Maintainer, Read-Only) Investigative preset. Run first when scoping any add / refactor / remove. Produces a structured report; writes no files in the repo. Workspace files under `.audit-workspace/` are allowed for T2/T3 sub-agent slices. ## Step 0: Triage Classify the request before any scan: - **T1** — single artifact type in scope (e.g., "is there already an agent for X?"). Inline scan; skip Step 4. - **T2** — 2-3 artifact types or one cross-reference dimension. 3 parallel sub-agents per Step 4. - **T3** — multi-pillar surface (e.g., touches agents + adapters + governance). 3 parallel sub-agents per Step 4 plus pillar-gap analysis. Record the tier in the Step 7 report header. ## Step 1: Preflight 1. Confirm clean working tree: `git status --short` returns empty. 2. Cache governance lean limits from `governance/CONSTITUTION.md` §2 P5. 3. Resolve target artifact type(s) from the prompt: agent, skill, rule, command, hook, adapter, pipeline module, governance file. 4. Note current branch: `git branch --show-current`. ## Step 2: Discover / Duplication Scan 5. Read `governance/inventory.json` — extract counts and ids for each artifact directory. 6. Grep across the canonical content surface for the target intent's keywords: ```bash grep -RIn --include='*.md' '<keyword1>\|<keyword2>' \ agents/ skills/ rules/ commands/ hooks/ \ checks/ prompts/ github-agents/ \ src/adapters/ src/content/ ``` 7. Cross...