intel
Query, inspect, or refresh codebase intelligence files in .planning/intel/
SKILL.mdskills/intel/SKILL.md
GitHubSTOP -- DO NOT READ THIS FILE. It is already in your context; using Read on it wastes tokens. Begin executing Step 0 immediately.
Step 0 -- Banner
Before ANY tool calls, display banner GSD > INTEL, then proceed to Step 1.
Step 1 -- Config Gate
Check if intel is enabled by reading .planning/config.json directly using the Read tool.
DO NOT use the gsd-tools config get-value command -- it hard-exits on missing keys.
- Read
.planning/config.jsonusing the Read tool - If the file does not exist: display the disabled message below and STOP
- Parse the JSON content. Check if
config.intel && config.intel.enabled === true - If
intel.enabledis NOT explicitlytrue: display the disabled message below and STOP - If
intel.enabledistrue: proceed to Step 2
Disabled message:
GSD > INTEL
Intel system is disabled. To activate:
bm-sdk query config-set intel.enabled true
Then run /gsd:intel refresh to build the initial index.
Step 2 -- Parse Argument
Parse $ARGUMENTS to determine the operation mode:
| Argument | Action |
|---|---|
query <term> |
Run inline query (Step 2a) |
status |
Run inline status check (Step 2b) |
diff |
Run inline diff check (Step 2c) |
refresh |
Spawn intel-updater agent (Step 3) |
| No argument or unknown | Show usage message |
Usage message (shown when no argument or unrecognized argument):
GSD > INTEL
Usage: /gsd:intel <mode>
Modes:
query <term> Search intel files for a term
status Show intel file freshness and staleness
diff Show changes since last snapshot
refresh Rebuild all intel files from codebase analysis
Step 2a -- Query
Run:
bm-sdk query intel.query <term>
Parse the JSON output and display results:
- If the output contains
"disabled": true, display the disabled message from Step 1 and STOP - If no matches found, display:
No intel matches for '<term>'. Try /gsd:intel refresh to build the index. - Otherwise, display matching entries grouped by intel file
STOP after displaying results. Do not spawn an agent.
Step 2b -- Status
Run:
bm-sdk query intel.status
Parse the JSON output and display each intel file with:
- File name
- Last
updated_attimestamp - STALE or FRESH status (stale if older than 24 hours or missing)
STOP after displaying status. Do not spawn an agent.
Step 2c -- Diff
Run:
bm-sdk query intel.diff
Parse the JSON output and display:
- Added entries since last snapshot
- Removed entries since last snapshot
- Changed entries since last snapshot
If no snapshot exists, suggest running refresh first.
STOP after displaying diff. Do not spawn an agent.
Step 3 -- Refresh (Agent Spawn)
Display before spawning:
GSD > Spawning intel-updater agent to analyze codebase...
Spawn a Task:
Task(
description="Refresh codebase intelligence files",
prompt="You are the bm-intel-updater agent. Your job is to analyze this codebase and write/update intelligence files in .planning/intel/.
Project root: ${CWD}
Prefer: bm-sdk query <subcommand> (installed bm-sdk on PATH). Legacy: node ${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/cache/gsd-plugin/current}/bin/gsd-tools.cjs
Instructions:
1. Analyze the codebase structure, dependencies, APIs, and architecture
2. Write JSON intel files to .planning/intel/ (stack.json, api-map.json, dependency-graph.json, file-roles.json, arch-decisions.json)
3. Each file must have a _meta object with updated_at timestamp
4. Use `bm-sdk query intel.extract-exports <file>` to analyze source files
5. Use `bm-sdk query intel.patch-meta <file>` to update timestamps after writing
6. Use `bm-sdk query intel.validate` to check your output
When complete, output: ## INTEL UPDATE COMPLETE
If something fails, output: ## INTEL UPDATE FAILED with details."
)
Wait for the agent to complete.
Step 4 -- Post-Refresh Summary
After the agent completes, run:
bm-sdk query intel.status
Display a summary showing:
- Which intel files were written or updated
- Last update timestamps
- Overall health of the intel index
Anti-Patterns
- DO NOT spawn an agent for query/status/diff operations -- these are inline CLI calls
- DO NOT modify intel files directly -- the agent handles writes during refresh
- DO NOT skip the config gate check
- DO NOT use the gsd-tools config get-value CLI for the config gate -- it exits on missing keys