Skip to content
Skills Library
Management & product · Writing

write-spec

/write-spec

Write docs/SPEC.md from the discovery files in docs/discovery/, or by interviewing the owner when there are none, and record the build decision as an ADR. Use when the owner asks to write or draft the spec. No code, no plan.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content17 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write docs/SPEC.md from the discovery files in docs/discovery/, or by interviewing the owner when there are none, and record the build decision as an ADR. Use when the owner asks to write or draft the spec. No code, no plan.

Original author description

Write docs/SPEC.md from the discovery files in docs/discovery/, or by interviewing the owner when there are none, and record the build decision as an ADR. Use when the owner asks to write or draft the spec. No code, no plan.

How it works

SKILL.md has no level-two headings · 18 lines, 244 words

SKILL.md preview
---
name: write-spec
description: Write docs/SPEC.md from the discovery files in docs/discovery/, or by interviewing the owner when there are none, and record the build decision as an ADR. Use when the owner asks to write or draft the spec. No code, no plan.
---

Write `docs/SPEC.md` as `docs/PROCESS.md` describes ("Spec").

1. Read `AGENTS.md`, `docs/PROCESS.md`, and the current `docs/SPEC.md`, including the prompts in its comments.
2. If `docs/discovery/` exists, read `OUTCOMES.md`, every brief in `research/`, and `DECISION.md`.
   - If `DECISION.md` is not **Accepted**, or its deliverable is not `app`, stop and say why. The spec waits for an accepted decision to build an app.
   - Otherwise copy the decision into `docs/decisions/` as the next numbered ADR (usually `0002-<short-title>.md`), in the format of `0000-template.md`, with status Accepted and the decision's date. Link the research briefs from its Context.
3. If there is no `docs/discovery/`, interview the owner one question at a time until every section of the spec can be filled in.
4. Fill every section of `docs/SPEC.md`:
   - Problem, Users and Success measures from the outcomes.
   - What they need to do as numbered goals.
   - Acceptance criteria in EARS form, numbered AC-1 onward, each one testable and each one a behavior, not a design choice.
   - The first build kept narrow: the smallest slice that is useful on its own. Everything else goes under Non-goals as a later feature.
   - Anything undecided under Open questions.
   Keep it to one to three pages. Remove the prompt comments.
5. Ask the owner about anything ambiguous, missing or contradictory, one question at a time, and record each answer in the spec.
6. Stop. Tell the owner to review and commit the spec, then run `/plan-build`. Write no code and no plan.

Versions

RepositoryScoreLicence
This page · happyotter1971/spec-harness82MIT
anhle9x/ai-worker100MIT
PranamRDoshi/dotclaude100MIT
allemaar/open-skills100Apache-2.0
dzhng/skills100MIT
zanderadam/engy100MIT
tojim00d/Orbit-skills100MIT
trihuynh-agilityio/workez100MIT
me2resh/apexyard100MIT

Database snapshot: 13.11.2026 · package version 9b955d95a415 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100spec
    Interview the user about a feature or project, then write a spec they can build from. Use when the user wants to plan, scope or spec something before coding, or runs /spec with an idea.
  • 95spec
    Create a specification with requirements, scenarios, and design rationale. Use when the user wants to write a spec, formalize requirements, convert an ADR to a specification, or says "create a spec".
  • 95feature-spec-creator
    Generates a feature spec for an existing codebase via an interview workflow. Use when the user wants to write, draft, or scope a feature spec — phrases like "write a feature spec", "spec out this feature", "draft a spec for X", "I want to add X to this codebase", "let's plan a…
  • 86adr
    Record an architecture decision as a short ADR in docs/adr and index it in docs/ARCHITECTURE.md. Use when a significant technical choice is made (state management, module boundaries, persistence, audio pipeline, a new shared pattern) or when the user asks to record or document a decision.
  • 90spec
    Write a spec to the owning workspace's specs/ folder from what the session already settled, with no new interview. Problem first, testable success criteria, and the seams to test. Use for /spec, or when someone says spec this out, write the plan, or turn this thread into a spec.
  • 100to-spec
    Turns the current conversation into a spec and publishes it to the project issue tracker, with no interview. Use when the user says \"write a spec\", \"create a PRD\", or wants the discussion captured as a spec.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.