Fetches requirements-clarity from softaworks/agent-toolkit and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/requirements-clarity
Restart Cursor to activate requirements-clarity. Access via /requirements-clarity in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
I understand your requirement. Let me help you refine this specification.
**Current Clarity Score**: X/100
**Clear Aspects**:
- [List what's clear]
**Needs Clarification**:
- [List gaps]
Let me systematically clarify these points...
Step 2: Gap Analysis
Identify missing information across four dimensions:
1. Functional Scope
What is the core functionality?
What are the boundaries?
What is out of scope?
What are edge cases?
2. User Interaction
How do users interact?
What are the inputs?
What are the outputs?
What are success/failure scenarios?
3. Technical Constraints
Performance requirements?
Compatibility requirements?
Security considerations?
Scalability needs?
4. Business Value
What problem does this solve?
Who are the target users?
What are success metrics?
What is the priority?
Step 3: Interactive Clarification
Question Strategy:
Start with highest-impact gaps
Ask 2-3 questions per round
Build context progressively
Use user's language
Provide examples when helpful
Question Format:
I need to clarify the following points to complete the requirements document:
1.**[Category]**: [Specific question]?
- For example: [Example if helpful]
2.**[Category]**: [Specific question]?
3.**[Category]**: [Specific question]?
Please provide your answers, and I'll continue refining the PRD.
After Each User Response:
Update clarity score
Capture new information in the working PRD outline
Identify remaining gaps
If score < 90: Continue with next round of questions
If score ≥ 90: Proceed to PRD generation
Score Update Format:
Thank you for the additional information!
**Clarity Score Update**: X/100 → Y/100
**New Clarified Content**:
- [Summarize new information]
**Remaining Points to Clarify**:
- [List remaining gaps if score < 90]
[If score < 90: Continue with next round of questions]
[If score ≥ 90: "Perfect! I will now generate the complete PRD document..."]
Step 4: PRD Generation
Once clarity score ≥ 90, generate comprehensive PRD.
Output File:
Final PRD: ./docs/prds/{feature_name}-v{version}-prd.md
Use the Write tool to create or update this file. Derive {version} from the document version recorded in the PRD (default 1.0).
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
