SkillSpec Writer
Turn a rough idea plus short answers into a structured spec draft: goal, audience, in scope, non-goals, requirements, and acceptance criteria, with a 9-point completeness score and every gap listed as an open question.
Works with: Claude Code, Codex, Cursor, Muse · Version 1.0.0 · Needs: Your brief: brief.txt (labelled lines — Title, Idea, Audience, Goal, plus In / Out / Need / Check / Constraint items).
Get this Skill with Premium See plans
Preview
Sample output
An example of what this Skill produces. Sample content, shown for illustration.
Spec Writer report — sample Completeness: 100/100 (9/9 required answers) | Gaps: 0 | Errors: 0 | Warnings: 0 Spec: BeanLoop Weekly Digest — Goal: Send one useful digest every Friday without manual assembly. Audience: Solo founders who ship weekly. In scope: Pull shipped items from the changelog; Group items by feature area. Non-goals: No social-media posting. Requirements: 3. Acceptance criteria: 2, including a short note for weeks with no shipped items. Constraint: Must run in under 5 minutes, local only. Open questions: None.
What you get
- A structured spec draft: goal, audience, idea, scope, non-goals, requirements, acceptance criteria, constraints
- A completeness score: 9 required slots, every gap as one open question
- Missing sections marked “Not yet defined” — never filled with invented content
- Every input error and warning named in the report
About this Skill
Reads one plain-text file you write — brief.txt, one labelled line per answer (Title / Idea / Audience / Goal, plus repeatable In / Out / Need / Check / Constraint lines) — and produces spec.md: the spec in fixed order carrying your words verbatim, a completeness score (round of 100 x filled / 9 required slots), every missing slot as an open question marked “Not yet defined”, and every input error and warning. Local-only, standard library only; nothing is invented to fill a gap — a 100/100 score means the brief is complete, not that the spec is good, and the draft still needs a human review before anyone builds from it.
Try it
Turn this rough idea and answers into a structured spec — goal, scope, non-goals, requirements, and acceptance criteria.Good fit
- Writing an idea down before anyone builds the wrong thing
- Agreeing scope and non-goals on paper, not in a meeting
- Checking a half-answered brief for exactly what is still missing
Not for
- Judging whether a spec is good — completeness is not quality
- Approving scope or effort — a draft is not a decision
- Inventing missing answers to raise the score
How to install
- Copy the install prompt into your agent:
Read https://skillu.dev/install/agent.md, then install the Spec Writer skill (spec-writer). - Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
- Call it with a slash command, e.g.
/spec-writer, and describe what you want in plain words.
FAQ
How is completeness scored?
Nine required slots: Title, Idea, Audience, Goal, at least one In item, at least one Out item, at least one Need item, at least one Check item, at least one Constraint item. Score = round(100 x filled / 9). A complete brief scores 100/100; a title-plus-idea brief scores 22/100.
What happens to a missing slot?
It stays “Not yet defined” in the draft and appears as one open question to answer. The script never guesses an audience, requirement, or constraint to raise the score.