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.
Datos de origen
- Repositorio
- RohiRIK/OpenLtm
- Última actividad en el origen
- 9 de octubre de 2026 a las 13:05
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 27
- Forks
- 2
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
2 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- 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
```
Ver en GitHub