SKILL41codebase-intelligence
Planning Codebase Changes with Evidence
Produces a scoped change evidence brief covering current state, affected surfaces, relevant paths, risks, open questions, candidate slices, and testing surfaces.
Primary benefit
Gives architecture, engineering planning, testing, or debugging a traceable handoff grounded in the codebase before executable work is designed.When to use
Use when a real codebase change needs a compact evidence brief that separates current-state facts, inferences, unresolved questions, affected surfaces, and possible implementation slices for the next owner.
When not to use
Do not use to produce or execute the implementation plan; Engineering Workflow owns executable planning through planning-engineering-work, while implementation methods own code changes.
Use cases
Prepare evidence for an engineering plan that changes behavior across several modules and contracts
Hand architecture or testing owners a bounded brief of current-state evidence, risks, gaps, and relevant verification surfaces
Example prompts
Use planning-codebase-changes-with-evidence to prepare a change evidence brief with scope, current state, affected surfaces, risks, unresolved questions, suggested slices, and testing surfaces. Label claims as observed, inferred, or unresolved and cite every source and location.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill planning-codebase-changes-with-evidencePowerShell
./install.ps1 --skill planning-codebase-changes-with-evidenceChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.