Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/project-specification
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
Passed 5 of 15 test cases with the skill, and 3 of 15 without it.
and 5 more in the full report
6 fixed2 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What command triggers the immediate next workflow step after completing specification?
| Checked | Without skill | With skill |
|---|---|---|
| References /attune:blueprint as the next step command | Missed | Passed |
The instructions your model reads when the skill loads.
For detailed specification writing workflows, this skill delegates to spec-kit:spec-writing as the canonical implementation. Use this skill for quick specification needs; use spec-kit for thorough specification documents.
Skill(attune:project-brainstorming) instead)Skill(attune:project-planning) instead)Skill(attune:war-room) for complex choices)With spec-kit:
Skill(spec-kit:spec-writing) for methodologyWithout spec-kit:
Carry the brief's Doc audience field into the specification, and treat it as a requirement rather than a note: it decides what the project's README, guides, and tutorials may contain. When the brief did not set one, ask, do not guess.
Specify the deep-dive destination alongside it, so extraction has
test cases passed, vs 3 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.