intel

STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 0 immediately.

Step 0 -- Banner

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► INTEL UPDATE                              ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

Step 1 -- Config Gate

Check if intel is enabled by reading .planning/config.json directly (do NOT use Bash for this -- config get throws on missing keys):

1. Read .planning/config.json
2. Check if intel.enabled is explicitly false
3. If false, display:

Intel system is disabled. Enable with: /pbr:config set intel.enabled true

Then STOP. Do not proceed further.

If enabled, not present, or no config file exists (all default to enabled), proceed to Step 2.

---

Step 2 -- Parse Argument

Parse the user's argument 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 or no argument	Spawn intel-updater agent (Step 3)

Step 2a -- Query

Run:

pbr-tools intel query <term>

Format and display the results. Show matching entries grouped by intel file. If no results found, suggest running refresh first.

STOP after displaying results. Do not spawn an agent.

Step 2b -- Status

Run:

pbr-tools intel status

Format and display staleness info for each intel file. Show last update times and whether files exist.

STOP after displaying status. Do not spawn an agent.

Step 2c -- Diff

Run:

pbr-tools intel diff

Format and display changes since the last full refresh. Show which files have changed and summary of differences.