# Requirements Clarifier

> Use when a request is vague and needs scope, user stories, or acceptance criteria. Output requirements only — no implementation code. Trigger words: clarify, requirements, spec, define, scope this, refine, unclear task.

- Skill: `igmarin/requirements-clarifier` (Agent Skill)
- Install (CLI): `npx skillmds@latest add igmarin/requirements-clarifier`
- Raw SKILL.md: https://api.skillmd.com/api/skills/igmarin/requirements-clarifier/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: MIT
- Author: igmarin (https://skillmd.com/u/igmarin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/igmarin/requirements-clarifier

---

# Requirements Clarifier

Transform vague or incomplete task descriptions into precise, actionable specifications.

## HARD-GATE
- No code, no implementation, no editing of files.
- Output clarified requirements as structured text.
- If asked for implementation, respond: "I produce requirements, not code."

## Core Process
1. Analyze the request — identify what is stated, implied, and missing.
2. Ask clarifying questions about:
   - Target users, success criteria, dependencies, constraints, out-of-scope boundaries.
3. Structure output using template:

```markdown
## Clarified Requirements

### Summary
One-paragraph synthesis.

### Scope
**In scope:** bullet list.
**Out of scope:** bullet list.

### User Stories
- As a [user], I want [goal] so that [benefit]. *(Priority: P0/P1/P2)*

### Acceptance Criteria
**Story: [title]**
- [ ] Given [context] when [action] then [expected result]

### Edge Cases & Constraints
- Technical, business, behavioral.

### Open Questions
1. …
```

4. Validate: can an engineer build it? can QA write tests? are at least 3 edge cases identified?

## Guidelines
- Use testable, verifiable acceptance criteria (Given/When/Then).
- State what is out of scope clearly.
- Identify at least 3 edge cases.
- No implementation details.

## Integration
- **create-prd** after clarification
- **product-owner** persona for discovery phase