discover

Name: discover
Availability: InStock
Author: fourthwiz

Scan project repositories and store inventory, architecture, and dependency maps in memory.

2|1|Updated Mar 18, 2026

Search Tags:#architecture #onboarding #memory #inventory #discover #repo-scanning

Ready to run

npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill discover-fourthwiz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/discover
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill discover-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans all repositories in the project folder to produce a persistent inventory, architecture overview, and dependency map that guide downstream planning, design reviews, and onboarding.

Core Features & Use Cases

Incremental repo discovery: detects changes and updates the memory artifacts to reflect the current project landscape.
Architecture overview: builds a map of cross-repo relationships and service boundaries for quick reference.
Dependency mapping: identifies core libraries, inter-service calls, and key integration points to inform planning and risk assessment.
Use case: run this when starting a new project or after significant repo changes to establish a baseline context for /architect, /plan, /critic, and /review.

Quick Start

Scan all repositories in the project folder and store an inventory, architecture map, and dependency graph in memory for downstream planning.

Frequently Asked Questions about discover

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

FAQPage Schema

How do I automatically map and inventory all repositories in my project folder?▼

You can automatically discover and inventory all repositories by scanning the project folder to generate a persistent architecture overview and dependency map for downstream planning tasks.

What is the best way to map cross-repo architecture and dependencies for onboarding?▼

Mapping cross-repo architecture involves identifying service boundaries and inter-service calls to produce a dependency graph, which establishes baseline context for onboarding and design reviews.

How do I maintain an up-to-date codebase inventory after significant repository changes?▼

You maintain an up-to-date codebase inventory through incremental repo discovery, which detects changes and updates memory artifacts to reflect the current project landscape.

Can I use generated dependency graphs to inform architecture planning and risk assessment?▼

Yes, you can use the generated dependency graphs to identify core libraries and key integration points, directly informing architecture planning, design reviews, and risk assessment.

Does this repo scanning approach store incremental updates to memory for downstream tasks?▼

Yes, the repo scanning approach stores incremental updates to memory artifacts, keeping context fresh for consumption by architecture, planning, critic, and review tasks.

When do I need to run cross-repo scanning to establish baseline context?▼

You need to run cross-repo scanning when starting a new project or after significant repository changes to establish a baseline context for downstream planning and reviews.