npx skills add smithery/ttmouse --skill requirements-clarifier
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.
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.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsArchitect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…
402.8K installsAlso in this package
Other skills from igmarin/agnostic-planning-skills · top by installs.
npx skills add 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.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
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.md1,893 B -
docs
SUMMARY.md251 B
History
- First seen on skills.sh
- 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
- Analyze the request — identify what is stated, implied, and missing.
- Ask clarifying questions about:
- Target users, success criteria, dependencies, constraints, out-of-scope boundaries.
- 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. …
- 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