discoverlisted

Feature research & ideation — frame a request, find prior art and reuse candidates in the repo (and optionally the web), then write a short feature brief and route onward. Read-only on app code; no spec, no plan, no implementation. TRIGGER when the user wants to research a feature, find prior art, check "what already exists for X", scope a fuzzy idea, or hunt for reuse before committing to a design ("research this", "what's already there", "how do we usually do X", "is there anything we can reuse"). Do NOT trigger when there is already a clear spec or scope → go to /prepare; or the request is a bug/failure → use /diagnose.
mik2win/foureyes · ★ 2 · AI & Automation · score 79

Install: claude install-skill mik2win/foureyes

# Feature Discovery: $ARGUMENTS The research step at the very front of the pipeline. You **frame** a request and surface **what already exists** before anyone writes a spec or a plan — so reuse opportunities and house patterns are found early, not after the fact. This skill carries ONLY invariant workflow logic. Every project-specific fact (plans location, architecture/module map, integrations) is read at runtime from `.claude/PROJECT.md`. You are **strictly read-only on app code** — you research and write a brief; you do not edit source, write a spec, or build a plan. Pipeline position: `/discover` (research) → `/analyst` (spec) → `/prepare` (plan) → `/implement` (code). --- ## Phase 0 — Load profile Before anything else, load context (this mirrors `skills/implement/SKILL.md`): 1. Read `.claude/PROJECT.md`. If it is missing, or still contains TEMPLATE / placeholder markers, fall back to the root `CLAUDE.md` (always in context) when it carries the stack/architecture/integrations below — proceed on it, noting you're running without a kit profile. Only if *neither* has those facts, **STOP** and tell the user: "Profile not configured — run `/bootstrap` to generate `.claude/PROJECT.md`, then re-run `/discover`." 2. If `$ARGUMENTS` is empty, ask the user what feature or question to research. 3. Read applicable `.claude/rules/*` (conventions, patterns) that bear on the area, and `CONTEXT.md` (the domain glossary) if present — frame the request in its vocabu