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.
Quellinformationen
- Repository
- RohiRIK/OpenLtm
- Letzte Quellaktivität
- 9. Oktober 2026 um 13:05
- Erkannte Sprache von SKILL.md
- Englisch
- Sterne
- 27
- Forks
- 2
Installationsoptionen
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Datei-Explorer
2 DateienSKILL.md wird angezeigt
SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau- 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
```
Auf GitHub ansehen