skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

discover

Analyze a codebase to identify implicit architectural decisions and spec-worthy subsystems.

30|2|Updated Feb 13, 2026
Search Tags:#architecture#documentation#codebase#analysis#drift#discover
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill discover-joestump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/discover
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill discover-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify implicit architectural decisions and spec-worthy subsystems within a codebase to guide documentation, governance, and future work.

Core Features & Use Cases

  • Systematically discover implicit architectural decisions and subsystems from the current codebase.
  • Produce a non-destructive discovery report that references existing ADRs and specs and highlights gaps for future documentation.
  • Facilitate governance by surfacing boundaries, subsystem responsibilities, and potential areas for formal ADRs or specs.

Quick Start

Run the discovery by issuing /design:discover [scope], or omit the scope to analyze the entire project.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I discover implicit architectural decisions in a codebase with no existing documentation?▼

Architectural discovery analyzes your codebase to surface implicit design decisions and spec-worthy subsystems, producing a structured report that highlights gaps for future documentation and governance.

What is the best way to reverse-engineer architecture and bootstrap ADRs from existing code?▼

Reverse-engineering architecture is best done by parsing codebase scope, loading existing ADRs, and analyzing subsystems in parallel to produce a non-destructive discovery report that references current specs and identifies missing ADRs.

Can I analyze the entire project or do I need to specify a scope for codebase architecture analysis?▼

Codebase architecture analysis supports both full-project and scoped reviews. You can issue a discovery command with a specific scope or omit it to systematically analyze the entire project's architectural boundaries and subsystem responsibilities.

How does architectural discovery handle existing ADRs and specs during codebase analysis?▼

Architectural discovery non-destructively loads existing ADRs and specs during analysis. It references them in the final report to map current governance and highlights undocumented areas where new formal ADRs are needed.

When do I need to unearth implicit architecture decisions from my source code?▼

You need to unearth implicit architecture decisions when preparing to bootstrap ADRs, improve governance, or reverse-engineer design artifacts to guide future documentation and development for an undocumented or drifting codebase.

Related Skills

Explore More Software Engineering Skills→
patrickrmoorepatrickrmoore

system-design

Draft and maintain a project-level Software Architecture Document in specs/sad.md.

Community
Advanced
asermaxasermax
1

analyze

Audit project documentation and generate a prioritized gap report.

Community
Advanced
knowz-ioknowz-io
1

explore

Analyze codebases and architecture to identify constraints, risks, and implementation options.

Official
Advanced
quangphu1912quangphu1912
1

tracing-dependencies

Detects circular dependencies, architectural violations, and conflicts in module graphs via static code analysis.

Community
Advanced