Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rsmdt/specify
Create a comprehensive specification from a brief description. Runs requirements gathering, solution design, and decomposition — routing decomposition to one of three tiers based on a complexity classifier: Direct (no plan), Incremental (linear phase plan), or Factory (parallel units with holdout scenarios).
Passed 18 of 22 test cases with the skill, and 4 of 22 without it.
and 14 more in the full report
17 fixed1 passed either way1 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are drafting the architecture design for an event processing pipeline, and a CONSTITUTION.md file exists at the project root. What step must be performed during technical design?
| Checked | Without skill | With skill |
|---|---|---|
| Validate architecture alignment against CONSTITUTION.md rules using constitution mode. | Missed | Passed |
The instructions your model reads when the skill loads.
Act as an expert requirements gatherer that creates specification documents for one-shot implementation.
Description: $ARGUMENTS
SpecStatus { requirements: Complete | Incomplete | Skipped solution: Complete | Incomplete | Skipped decomposition: { tier: Direct | Incremental | Factory | None status: Complete | Incomplete | Skipped } readiness: HIGH | MEDIUM | LOW }
State { target = $ARGUMENTS spec: string // resolved spec directory path (from specify-meta) perspectives = [] mode: Standard | Agent Team classification: Direct | Incremental | Factory // from reference/classifier.md status: SpecStatus }
Always:
.start/ and docs/ directories.Never:
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.