dev-discovery

Coordinate technical discovery and generate a discovery artifact for dev planning.

Updated Oct 8, 2025
One-click install
npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill dev-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-discovery
Source: https://github.com/ichabodcole/project-docs-scaffold-template/tree/main/plugins/project-docs/skills/dev-discovery
Command: npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill dev-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-planning technical discovery for complex features. Orchestrates explorers to gather codebase context, validates architecture docs, and prepares comprehensive input for the dev-plan-generator.

Core Features & Use Cases

  • Orchestrates parallel explorers to gather codebase context and validate architecture documentation.
  • Checks architecture docs and creates or updates them as needed, producing usable artifacts for planning.
  • Generates a discovery artifact at .claude/discoveries/YYYY-MM-DD-<feature-name>-discovery.md and feeds the dev-plan-generator with complete context.

Quick Start

Initiate a dev-discovery run for a feature, spawn explorers, and produce a discovery document for planning.

Frequently Asked Questions about dev-discovery

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

FAQPage Schema
How do I do technical discovery for complex features across multiple systems?

Technical discovery for complex features is coordinated by orchestrating parallel explorers to gather codebase context and validate architecture docs before development planning begins.

When do I need to run pre-planning architecture discovery?

Pre-planning architecture discovery is needed when starting work on complex features spanning multiple files or systems, ensuring architecture documentation is validated and updated before development.

How do I generate a discovery artifact for development planning?

Generate a discovery artifact by spawning explore agents to collect codebase context, verifying documentation status, and producing ephemeral output at .claude/discoveries/YYYY-MM-DD-feature-discovery.md for handoff.

What is the best way to validate architecture docs before planning a feature?

Validating architecture docs before feature planning involves checking existing documentation status and creating or updating them as needed to produce usable artifacts for the development planning process.

Can I feed codebase exploration results directly into a dev plan generator?

Codebase exploration results can be fed into a dev plan generator by orchestrating parallel explorers to gather context and producing a comprehensive discovery artifact as complete input.

Does technical discovery work for features spanning multiple files and systems?

Technical discovery applies specifically when starting work on complex features across multiple files or systems, orchestrating explorers to gather the necessary codebase context for planning.