igmarin/agnostic-planning-skills

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.

First seen Jun 19, 2026

Installation

$ npx skills add igmarin/agnostic-planning-skills --skill requirements-clarifier

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from igmarin/agnostic-planning-skills · top by installs.

npx skills add igmarin/agnostic-planning-skills

Browse all from igmarin/agnostic-planning-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
More metadata
version
1.0.0
user-invocable
true
output
Clarified requirements with user stories, acceptance criteria, edge cases, open questions
constraints
NO CODE — produces requirements only.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,893 B
  • docs SUMMARY.md 251 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 23 installs

SKILL.md

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.

  1. Structure output using template:
## 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. …
  1. 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