ZaneL1u/gsd-intel

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-intel or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Cursor tools when executing GSD workflows:

• Shell for running commands (terminal operations)
• StrReplace for editing existing files
• Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter>

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

Step 0 -- Banner

Before ANY tool calls, display this 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.

1. Read .planning/config.json using the Read tool
2. If the file does not exist: display the disabled message below and STOP
3. Parse the JSON content. Check if config.intel && config.intel.enabled === true
4. If intel.enabled is NOT explicitly true: display the disabled message below and STOP
5. If intel.enabled is true: proceed to Step 2

Disabled message:

GSD > INTEL

Intel system is disabled. To activate:

  node /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/bin/gsd-tools.cjs config-set intel.enabled true

Then run /gsd-intel refresh to build the initial index.

---

Step 2 -- Parse Argument

Parse {{GSD_ARGS}} 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:

node /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/bin/gsd-tools.cjs 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:

node /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/bin/gsd-tools.cjs intel status

Parse the JSON output and display each intel file with:

• File name
• Last updated_at timestamp
• 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:

node /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/bin/gsd-tools.cjs 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 gsd-intel-updater agent. Your job is to analyze this codebase and write/update intelligence files in .planning/intel/.

Project root: ${CWD}
gsd-tools path: /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/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 gsd-tools intel extract-exports <file> to analyze source files
5. Use gsd-tools intel patch-meta <file> to update timestamps after writing
6. Use gsd-tools 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:

node /Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/bin/gsd-tools.cjs intel status

Display a summary showing:

• Which intel files were written or updated
• Last update timestamps
• Overall health of the intel index

---

Anti-Patterns

1. DO NOT spawn an agent for query/status/diff operations -- these are inline CLI calls
2. DO NOT modify intel files directly -- the agent handles writes during refresh
3. DO NOT skip the config gate check
4. DO NOT use the gsd-tools config get-value CLI for the config gate -- it exits on missing keys