forge-discover

Classifies idea complexity and routes work to the appropriate specification or issue workflow.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-discover-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-discover
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-discover
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-discover-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often over-engineer small tasks with full specs or under-plan large initiatives. This Skill triages a raw idea by assessing its complexity and routes it to the right workflow entry point, preventing wasted planning effort and under-scoped work. ## Core Features & Use Cases - Complexity Classification: Uses a Sonnet exploration agent to scan affected files, service boundaries, and ADRs, then classifies work as Trivial, Low, Medium, High, or Epic. - Workflow Routing: Recommends the correct next step, such as direct issue shaping for small tasks or full spec analysis for architecture-heavy work. - Overlap Detection: Searches existing GitHub issues and specs to surface duplicate or related work before creating new artifacts. - Use Case: A developer says "we should add caching to the API." The Skill scans the repo, finds it touches 3 files in one service, classifies it as Low complexity, and routes directly to issue creation instead of a full spec. ## Quick Start Ask the assistant to triage your idea by describing what you want to build, and it will assess the scope and recommend the right workflow entry point.

Frequently Asked Questions about forge-discover

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

FAQPage Schema
How do I decide whether an idea needs a spec or just an issue?

Run a complexity triage that scans affected files, service boundaries, and architecture decision records. Ideas touching 1-5 files in a single service go straight to issue shaping, while larger or ADR-governed work gets routed to full specification.

How to triage feature ideas before writing a specification?

Describe the idea, let an exploration agent assess which files and systems it touches, then classify it as Trivial, Low, Medium, High, or Epic. Each classification maps to a recommended entry point such as issue shaping or spec writing.

Does this skill create GitHub issues or write specs?

No, it only classifies complexity and recommends a route. Issue creation is handled by the forge-shape skill and spec writing by the forge-spec skill, keeping each workflow step single-purpose.

Can the routing decision proceed without user confirmation?

Yes, when CLAUDE_MODE is set to autonomous and the issue lacks a needs-human-gate label, routing auto-confirms. In supervised mode or when the label is present, it waits for explicit user confirmation.

What happens when an idea is too large for one spec?

Ideas classified as Epic are decomposed into two to four spec-worthy chunks with the user's help. Each chunk is then prioritized and routed individually through the specification workflow.