Skip to content
Skills Library
Management & product · Writing

spec

/spec

Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.

Repository
backlog ↗
Licence
MIT
Last repository change
30.05.2026

Assessment and security

90/ 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.
Content25 / 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 30.05.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 a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.

Original author description

Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.

How it works

  1. Process
Original SKILL.md headings · 22 lines, 190 words
SKILL.md preview
---
name: spec
description: Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.
---

# Write Task Spec

Write a specification document for a task. If an argument is provided, use it as the task ID or description to find the task. Otherwise, ask which task to spec.

## Process

1. **Find the task** — use `task_list` or `task_info` to find the task matching "$ARGUMENTS". If $ARGUMENTS is empty, call `task_list` with filter `status:pending -doc` to show tasks without specs and ask which one.

2. **Understand the context** — read relevant code, configs, and existing docs in the codebase to understand what the task involves.

3. **Write the spec** — use `task_doc_write` to attach a markdown document to the task with:
   - **Goal**: what this task achieves
   - **Requirements**: specific things that must be built or changed
   - **Technical approach**: key decisions and implementation strategy
   - **Acceptance criteria**: how to verify the task is done
   - **Relevant code**: file paths and functions to modify

4. **Confirm** — show a summary of the spec that was written and the task it was attached to.

Keep specs concise and actionable — a spec should be something an agent can pick up and implement without further context.

Versions

RepositoryScoreLicence
This page · backloghq/backlog90MIT
renzrollon/interlock100MIT
CodaColaLight/nightmill100Apache-2.0
duronext/jig100MIT
optiflowic/keyturn100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
flavien-ia/hypervibe-craft100Apache-2.0

Database snapshot: 13.11.2026 · package version 6f344a262aea (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

  • 100write-acceptance-criteria
    Use when the user asks to define acceptance criteria, write a spec for a task, clarify what "done" looks like, or translate a vague goal into testable requirements. Triggers on "acceptance criteria", "definition of done", "how will we know this works", "spec for".
  • 100writing-acceptance-criteria
    Use when a spec document has been approved during brainstorming and you need to produce testable acceptance criteria before writing the implementation plan - converts spec requirements into a structured acceptance criteria document
  • 100sdd
    Use this skill when the user wants a written spec, acceptance criteria, or a task graph before a non-trivial implementation, or runs the WrongStack /sdd workflow. Triggers: user says "/sdd", "spec", "specification", "task graph", "SDD", "acceptance criteria".
  • 100product-manager
    Product Manager / Requirements Analyst role skill. Use when you need to model requirements, produce structured output, define MVP scope, write user stories, define acceptance criteria, or turn a one-sentence idea into a deliverable detailed requirements document. Keywords:…
  • 95memstack-product-feature-spec
    Use this skill when the user says 'feature spec', 'spec this feature', 'write a spec', 'functional requirements', or needs a detailed specification for one feature with user flows, edge cases, API definitions, and acceptance criteria. Do NOT use for full PRDs or user story generation.
  • 95strata.spec
    Use when a feature or change needs its requirements, acceptance criteria and constraints written or revised before planning; when a planning document exists but has no desired specification; when the user says what to build, acceptance criteria, requirements, or asks whether the…

Feedback and reports

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