requirements-clarifier

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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
- The `product-owner` intent in `work-router` can focus discovery goals; `requirements-clarifier` owns the clarification output.

From igmarin/agnostic-planning-skills, MIT.

More from igmarin/agnostic-planning-skills