shamt-discovery

Conduct structured epic discovery and generate DISCOVERY.md with recommended approach.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shamt-discovery
Source: https://github.com/MizunoPK/shamt-ai-dev/tree/main/.claude/skills/shamt-discovery
Command: npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery phase is mandatory for every epic and ensures a structured research workflow that surfaces questions, risks, and scope before feature planning, reducing rework later.

Core Features & Use Cases

  • Structured research across six brainstorm categories to surface issues and questions
  • DISCOVERY.md generation with executive summary, technical analysis, solution options, and recommended approach
  • Validation loop orchestration including primary clean rounds and sub-agent confirmations to ensure quality
  • User approval workflow to confirm findings before moving to feature breakdown

Quick Start

Run the discovery phase for an epic by initiating the S1 discovery flow and following prompts to complete DISCOVERY.md

Frequently Asked Questions about shamt-discovery

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

FAQPage Schema
What is epic discovery and why do I need it before feature planning?

Epic discovery is a structured research phase that surfaces questions, risks, and scope before feature planning. You need epic discovery to reduce rework later by validating the problem space and documenting findings in DISCOVERY.md.

How do I automate epic discovery and generate a DISCOVERY.md file?

Automate epic discovery by initiating the S1 discovery flow to read architecture docs and brainstorm across six categories. The system runs iterative validation loops to produce a complete DISCOVERY.md with recommended approach and feature breakdown.

How does the validation loop work during the problem space discovery process?

The validation loop works by running iterative discovery rounds until a primary clean round and sub-agent confirmations are achieved. This ensures quality control and validates findings before moving to feature breakdown.

Can I use this structured discovery workflow for any scale of epic planning?

You can use this structured discovery workflow for any epic planning scale because the process is mandatory for every epic. It adapts to your architecture docs to ensure prerequisites and exit criteria are met regardless of project size.

What is included in the generated DISCOVERY.md document?

The generated DISCOVERY.md document includes an executive summary, technical analysis, solution options, and a recommended approach. It also contains a feature breakdown confirmed through a user approval workflow.

When should I not use an automated discovery phase for epic planning?

You should not use an automated discovery phase when you lack existing architecture docs for the system to read, as this workflow relies on parsing those documents to brainstorm across its six categories and validate the problem space.