davepoon/gsd:intel
plugins/gsd/skills/intel/SKILL.md
Query, inspect, or refresh codebase intelligence files in .planning/intel/
$ install --global
skillsauthnpx skillsauth add davepoon/buildwithclaude gsd:intelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 4:20 PM9.4s1 file scanned
SKILL.md
- name:
- gsd:intel
- description:
- Query, inspect, or refresh codebase intelligence files in .planning/intel/
- argument-hint:
- [query <term>|status|diff|refresh]
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code'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.
- 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:
gsd-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:
gsd-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:
gsd-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:
gsd-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 gsd-intel-updater agent. Your job is to analyze this codebase and write/update intelligence files in .planning/intel/.
Project root: ${CWD}
Prefer: gsd-sdk query <subcommand> (installed gsd-sdk on PATH). Legacy: node $HOME/.claude/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-sdk query intel.extract-exports <file>` to analyze source files
5. Use `gsd-sdk query intel.patch-meta <file>` to update timestamps after writing
6. Use `gsd-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:
gsd-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
Related Skills
davepoon/whats-next
tools
VerifiedTrustedCommunity
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
3,021SKILL.mdUpdated Jun 5, 2026
davepoon/using-startup-superpowers
data-ai
VerifiedTrustedCommunity
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
3,021SKILL.mdUpdated Jun 5, 2026
davepoon/surveys
tools
VerifiedTrustedCommunity
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
3,021SKILL.mdUpdated Jun 5, 2026
davepoon/mvp
development
VerifiedTrustedCommunity
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.
3,021SKILL.mdUpdated Jun 5, 2026