requirement-enhancer
Rewrites vague or incomplete requirements into precise, testable statements — filling in quantities, actors, conditions, and error behavior while preserving intent. Use after ambiguity-detector flags problems, when a requirement can't be turned into a test, or when engineers keep asking the same clarification questions.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill requirement-enhancer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what the skill does (rewrites requirements with specific details like quantities, actors, conditions) and when to use it (after ambiguity detection, when requirements aren't testable, or when clarification questions recur). The description uses proper third-person voice and includes natural trigger terms that engineers would use. The reference to the ambiguity-detector skill helps position this in a workflow context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Rewrites vague or incomplete requirements into precise, testable statements' and explicitly names what gets filled in: 'quantities, actors, conditions, and error behavior while preserving intent.' | 3 / 3 |
Completeness | Clearly answers both what ('Rewrites vague or incomplete requirements into precise, testable statements') AND when ('Use after ambiguity-detector flags problems, when a requirement can't be turned into a test, or when engineers keep asking the same clarification questions'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'requirements', 'testable', 'ambiguity', 'clarification questions', 'vague', 'incomplete'. These are terms engineers and product managers naturally use when dealing with requirement issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on requirement rewriting with distinct triggers tied to ambiguity detection and testability concerns. References a specific upstream skill (ambiguity-detector) which further clarifies its role in a workflow. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently teaches requirement enhancement through concrete patterns, a detailed worked example, and a structured output format with built-in validation. The testability checklist and enhancement patterns table provide immediately actionable guidance, while the 'Do not' section prevents common mistakes. The skill respects Claude's intelligence while providing the domain-specific knowledge needed for this task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The tables are dense with information, the worked example is necessary for understanding, and there's no explanation of concepts Claude already knows. The 'Do not' section efficiently captures common pitfalls without padding. | 3 / 3 |
Actionability | Highly actionable with concrete enhancement patterns, a complete worked example showing before/after transformation, and a specific output format template. The testability checklist provides exact questions to answer, and the enhancement patterns table gives copy-paste-ready templates. | 3 / 3 |
Workflow Clarity | Clear workflow: input (vague requirement + stakeholder answers) → apply testability checklist → use enhancement patterns → output in specified format. The output format itself includes validation via the 'Testability check' table that forces verification each requirement can be tested. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections that build logically: checklist → patterns → worked example → decomposition guidance → anti-patterns → output format. At ~120 lines for a complex skill, the content is appropriately contained in a single file with no need for external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.