Install any skill in seconds. Free to start, no credit card required.
Get Started Free →miosa-osa/spec
/spec <feature_name> [--depth brief|full]
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
and 6 more in the full report
10 fixed8 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please construct a comprehensive technical specification for a background job processing system. It should outline the system objectives, exact requirements, structural design, API contracts, verification test steps, and a rollback process.
| Checked | Without skill | With skill |
|---|---|---|
| Includes numbered requirements with explicit acceptance criteria | Missed | Passed |
| Includes a test plan detailing verification steps and edge cases | Missed | Passed |
| Includes a rollback plan detailing deployment revert steps | Missed | Passed |
The instructions your model reads when the skill loads.
/spec <feature_name> [--depth brief|full]
Generate a technical specification for a feature or system change.
| Arg | Type | Required | Description |
|---|---|---|---|
| feature_name | string | Yes | Feature to spec |
| --depth | string | No | Spec depth: brief (1-page) or full (complete). Default: full |
Genre: spec Format: Markdown technical specification
Produces:
1. Tech-lead defines requirements and constraints
2. Architect designs system integration and API contracts
3. Combined into single spec document per tech-lead's template
4. Tech-lead reviews and approves final spec
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.