gsd-intel

Document codebase structure and dependencies into an Intel markdown file.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-intel-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-intel
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/gsd-intel
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-intel-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly orient themselves in an unfamiliar codebase before planning or implementing changes.

Core Features & Use Cases

  • Identify entry points, models, configuration files, and tests to map the feature area.
  • Read architecture to understand directory structure, abstractions, dependencies, and testing approach.
  • Document Intel by creating .planning/intel/<feature>-intel.md with sections for entry-point, models, config, architecture, patterns, and questions.

Quick Start

Run gsd-intel on the target feature to generate an Intel document detailing key files, architecture, and questions.

Frequently Asked Questions about gsd-intel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orient myself in an unfamiliar codebase before planning new features?

To orient in an unfamiliar codebase before planning, identify entry points, models, configuration files, and tests to map the feature area. Document these findings in a structured Intel file to build a mental model of structure, dependencies, and conventions.

What is the best way to document codebase architecture and dependencies for onboarding?

Documenting codebase architecture for onboarding involves reading directory structures, abstractions, and testing approaches, then creating an Intel document with sections for entry points, models, config, architecture, patterns, and questions.

Can I generate a planning document for codebase structure and patterns automatically?

Yes, you can generate a planning document by running an intelligence skill on the target feature. It produces an Intel markdown file detailing key files, architecture, patterns, and questions to guide informed planning.

Does this codebase intelligence approach work for understanding testing approaches and conventions?

Yes, codebase intelligence reads architecture to understand testing approaches and conventions. It maps the feature area by identifying entry points and configuration files, capturing these patterns in an Intel document.

How do I map entry points and configuration files when exploring a new codebase?

To map entry points and configuration files in a new codebase, read the architecture to understand directory structure and abstractions. Document these elements alongside models and architecture patterns in an Intel markdown file.

When should I use an Intel document for codebase engineering planning?

Use an Intel document for codebase engineering planning at the start of new features or when entering unfamiliar areas. It builds a mental model of dependencies and conventions, enabling informed planning before implementation.