Spec
/Spec
Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria' before planning or implementing a feature or bug fix.
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria' before planning or implementing a feature or bug fix.
Triggers from the description
Original author description
Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria' before planning or implementing a feature or bug fix.
How it works
- Workflow Routing
- Examples
SKILL.md preview
--- name: Spec description: "Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria' before planning or implementing a feature or bug fix." user-invocable: false --- # Spec Before writing a spec, explore the codebase and recall prior decisions from LTM. Produces acceptance criteria that feed directly into planning (the `ltm-planner` agent) and into tests. LTM tools and the recall → learn ritual live in one place: the **Ltm** skill ([../Ltm/SKILL.md](../Ltm/SKILL.md)). ## Workflow Routing | Workflow | Trigger | File | |----------|---------|------| | **ExploreAndSpec** | "spec", "define what to build", "requirements", "acceptance criteria", "before we plan" | [Workflows/ExploreAndSpec.md](Workflows/ExploreAndSpec.md) | ## Examples **Example 1: New feature on existing project** ``` User: "Spec out rate limiting for the API" → recall + context for auth/API decisions → Explores existing middleware and route files → Writes spec with acceptance criteria into specs/ → Hands off to the ltm-planner agent ``` **Example 2: Bug investigation** ``` User: "Write a spec for the session token expiring too early" → recall for session/auth gotchas → Explores auth files and session logic → Writes spec with reproduce steps and acceptance criteria → Hands off to a failing test built from those criteria ```
Files in this package (2)
- SKILL.md 2 KB
- Workflows/ExploreAndSpec.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rohirik/openltm | 90 | MIT |
| renzrollon/interlock | 100 | MIT |
| CodaColaLight/nightmill | 100 | Apache-2.0 |
| duronext/jig | 100 | MIT |
| optiflowic/keyturn | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| flavien-ia/hypervibe-craft | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 324be1bcaa69 (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
- 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 - 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". - 95wicked-garden-product-acceptance-criteria
Define testable acceptance criteria from requirements and design. Bridge product requirements with QE test scenarios. Use when: "define acceptance criteria", "how do we know it's done", "what should QE test", "definition of done - 90write-spec
Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing. - 100v-spec
Write the spec and plan for one piece of work in a v-start project (specs/N-name/spec.md and plan.md), grounded in the real source, with a belief, a pass mark and numbered acceptance criteria, then stop for approval. Use when the user says "/v-spec", "write a spec", "spec this",… - 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.