requirements-engineer
tessl i github:martinellich/aiup-marketplace --skill requirements-engineerGathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints. Use when the user asks to "write requirements", "create a PRD", "gather requirements", "document feature specs", "write user stories", "define NFRs", "list constraints", or mentions requirements catalog, requirements analysis, product requirements document, or feature specification.
Validation
88%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
Implementation
77%This is a well-structured skill with excellent actionability through concrete table formats and examples. The workflow is clear with proper validation checkpoints and error recovery. However, it could be more concise by removing reference tables for concepts Claude already understands (priority levels, status definitions, NFR categories) and potentially splitting reference material into a separate file.
Suggestions
Remove or significantly condense the Priority Reference, Status Reference, NFR Categories Reference, and Constraint Categories Reference tables - Claude understands these concepts and can infer appropriate values from the examples
Consider moving the reference tables to a separate REFERENCE.md file and linking to it, keeping SKILL.md focused on the core workflow and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with good use of tables, but includes some redundant reference tables (Priority, Status, NFR Categories, Constraint Categories) that Claude already knows. The examples are helpful but the reference sections add bulk without unique value. | 2 / 3 |
Actionability | Highly actionable with concrete table formats, specific examples for each requirement type, clear ID prefixes, and explicit quality checks with good/bad examples. The user story format is precisely defined and immediately usable. | 3 / 3 |
Workflow Clarity | Clear 8-step workflow with explicit validation step (step 7) that includes specific checks. Error recovery section provides feedback loops for common issues like ambiguous requirements and conflicts. The DO NOT section adds clear guardrails. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in a single file. The reference tables (Priority, Status, Categories) could be split into a separate reference file to keep the main skill leaner. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users would naturally use, explicit 'Use when' guidance, and clear domain boundaries that distinguish it from other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Gathers, organizes, and documents software requirements' with explicit outputs including 'functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints'. | 3 / 3 |
Completeness | Clearly answers both what (gathers, organizes, documents requirements into structured catalogs with specific components) AND when (explicit 'Use when' clause with comprehensive trigger phrases and terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'write requirements', 'create a PRD', 'gather requirements', 'document feature specs', 'write user stories', 'define NFRs', 'list constraints', 'requirements catalog', 'requirements analysis', 'product requirements document', 'feature specification'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on software requirements documentation with distinct triggers like 'PRD', 'NFRs', 'requirements catalog', and 'feature specification' that are unlikely to conflict with general documentation or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.