Menu
Explores code + LTM, then writes acceptance criteria. USE WHEN defining what to build before planning.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
USE WHEN separating trusted instructions from untrusted content or tool output.
USE WHEN hardening command execution, path handling, or installer boundaries.
USE WHEN handling credentials, env vars, logs, tests, or docs safely.
Reference for LTM memory commands, context hooks, and DB schema; use when the user mentions learning, recalling, forgetting, relating, or capturing memory, or when a session starts or the project changes.
Mines LTM memories from past git commits. Use when onboarding a repo into LTM, backfilling history after enabling gitLearn, or harvesting patterns after a sprint.
Reference for retrieved patterns and lessons from past sessions; use when prior fixes, gotchas, decisions, or earlier sessions may apply, or when asked what we learned before.
| name | Spec |
| description | Explores code + LTM, then writes acceptance criteria. USE WHEN defining what to build before planning. |
| user-invocable | false |
Before writing a spec, explore the codebase and recall prior decisions from LTM. Produces acceptance criteria that feed directly into /plan.
LTM tools and the recall → learn ritual live in one place: SkillSearch('ltm memory contract') loads the Ltm skill.
| Workflow | Trigger | File |
|---|---|---|
| ExploreAndSpec | "spec", "define what to build", "requirements", "before plan" | Workflows/ExploreAndSpec.md |
Example 1: New feature on existing project
User: "/spec add rate limiting to the API"
→ recall + context for auth/API decisions
→ Explores existing middleware and route files
→ Writes spec with acceptance criteria into specs/
→ Hands off to /plan
Example 2: Bug investigation
User: "/spec the session token expires too early"
→ recall for session/auth gotchas
→ Explores auth files and session logic
→ Writes spec with reproduce steps and acceptance criteria
→ Hands off to /test (ProveIt)