specmint-corelisted

Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
ngvoicu/kluris · ★ 4 · AI & Automation · score 77

Install: claude install-skill ngvoicu/kluris

# Spec Mint Core Turn ephemeral plans into structured, persistent specs built through deep research and iterative interviews. Specs have phases, tasks, acceptance criteria, a registry, resume context, a decision log, and a deviations log. They live in `.specs/` at the project root and work with any AI coding tool that can read markdown. Whether `.specs/` is committed is repository policy. Respect `.gitignore` and the user's preference for tracked vs local-only spec state. ## Critical Invariants 1. **Single-file policy**: Keep this workflow in one `SKILL.md` file. 2. **Canonical paths**: - Registry: `.specs/registry.md` - Per-spec files: `.specs/<id>/SPEC.md`, `.specs/<id>/research-*.md`, `.specs/<id>/interview-*.md` 3. **Authority rule**: `SPEC.md` frontmatter is authoritative. Registry is a denormalized index for quick lookup. 4. **Active-spec rule**: Target exactly one active spec at a time. 5. **Parser policy**: Use best-effort parsing with clear warnings and repair guidance instead of hard failure on malformed rows. 6. **Progress tracking is sacred**: After completing any task, immediately update SPEC.md (checkbox, `← current` marker, phase marker) AND registry.md (progress count, date). Then re-read both files to verify the edits landed correctly. Never move to the next task without updating both files. Never end a session with the registry out of sync with SPEC.md. This is non-negotiable — if you do nothing else, do this. ## Session