Install any skill in seconds. Free to start, no credit card required.
Get Started Free →griddynamics/requirements-authoring-flow
Workflow for authoring requirements and specifications: drafting, review, validation, etc.
Passed 15 of 22 test cases with the skill, and 5 of 22 without it.
and 13 more in the full report
11 fixed4 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are running Phase 2 (Research) to gather industry compliance standards for HIPAA-compliant medical record storage requirements. Which subagent role and required model class must be assigned to this phase?
| Checked | Without skill | With skill |
|---|---|---|
| The response assigns Phase 2 research to the requirements-engineer subagent. | Missed | Passed |
| The response specifies the gpt-5.6-sol-high model for the research subagent. | Missed | Passed |
The instructions your model reads when the skill loads.
<description_and_purpose>
Prevents premature drafting by enforcing HITL gates where every <req> unit receives explicit user approval before proceeding. Each phase produces traceable artifacts (Final Requirements Set, Validation Pack, Traceability Matrix). Input: user request for new requirements, edits, review, refactor, or validation; USE SKILL requirements-authoring and PROACTIVELY REQUIRE its use in all phases and subagents.
</description_and_purpose>
<workflow_phases>
<prerequisites phase="0", applies="ALL">
load-project-context, hitlrequirements-authoring-flow-state.md in FEATURE TEMP with: phase name, status, artifact produced, and open questions.requirements-authoring.reverse-engineering./goal is set repeat phases 5-6 until goal is met, then continue with the rest of phases.IMPORTANT! If the task is to reverse engineer requirements, spawn MULTIPLE subagents with each handling one unit of analysis (one screen, one page, one controller, one endpoint, etc) to effectively prevent hallucinations by narrow scoping for phases intent_capture, outline, draft, validate.
Artifact: Discovery Summary (context, existing requirements, constraints, affected files). Done when: scope boundaries and relevant requirement files are identified.
requirements-authoringreverse-engineeringtest cases passed, vs 5 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.