requirements-elicitlisted

Runs the requirements-elicitation interview methodology from spec/project/requirements-elicitation/ to capture a user's requirements precisely, assuming the user often does not know exactly what they want, expresses it imperfectly, or is misread. Drives a one-question-at-a-time funnel interview, maintains a per-dimension confidence score plus a gap matrix, asks confidence-gated clarifying questions only where understanding is weak, and writes an authoritative artifact to project/requirements/<slug>.md. Invoke when the user says things like "elicit the requirements for X" or "I want to build something but I'm not sure what exactly", or equivalent German-language requests. Also triggers as the upstream gate of roadmap-plan, feature-decompose, and issue-orchestrate when a requirement artifact is missing or below threshold. Don't use to decompose an existing requirement set (use feature-decompose) or author the downstream spec (use spec). Supports resume per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · Web & Frontend · score 76

Install: claude install-skill nolte/claude-shared

# Requirements Elicitation Skill Operationalizes `spec/project/requirements-elicitation/` so a development request becomes a precise, confidence-scored requirement set instead of the agent's first plausible guess. The method is engineered against the default case: the user often **does not know exactly what they want**, **expresses it imperfectly**, or **is misread**. It drives understanding up to a measured threshold *before* anything downstream is built. ## Why this is a skill, not an agent - **Mid-flow interactivity is the contract** — the spec mandates a one-question-at-a-time funnel interview with teach-back confirmation per requirement. Each turn shows one question, reads the user's answer, and lifts the lowest-confidence dimension; an agent's isolated, non-interactive context cannot run that dialogue. - **Persistent on-disk artifact** — the result (requirement list + filled gap matrix + surviving assumptions) lives at `project/requirements/<slug>.md` and is read by downstream consumers (`roadmap-plan`, `feature-decompose`, `issue-orchestrate`). A skill owns persistent state; an agent returns a report and forgets. - **`confirmed` vs `assumed` and teach-back need the user in the loop** — the spec forbids marking a requirement `confirmed` without an explicit teach-back confirmation; that signal can only be gathered interactively. - Counter-dimension considered: a read-only agent could later score the gap matrix on a finished artifact (a `validate`-style audit), but the