Stats
Actions
Available In
Tags
Plugin
spec-mirror
Generate, drift-check, lint, test-stub, coverage-audit and scope-walk E2E specs against the current implementation. A six-skill safety net for keeping code, spec, tests, and team knowledge in sync.
What's Inside
Skills6
compare
/compare
Drift-check the current implementation against the existing specs/ directory. Use when the user wants to verify the spec is still accurate, catch undocumented changes, or run the safety-net check after recent code edits. Triggers include "spec compare", "drift check", "verify spec", "is the spec stale", "check spec drift", "스펙 비교", "스펙 드리프트", "스펙 확인", "스펙 검증". Produces specs/DRIFT.md categorizing added / removed / changed elements per layer and per flow, with severity ratings. Does NOT modify the existing specs — only reports.
coverage
/coverage
Cross-reference existing tests against the specs/ directory to find untested flows, endpoints, and invariants. Use when the user wants to see how much of the spec is actually covered by tests, before relying on the test suite as a safety net. Triggers include "spec coverage", "test coverage vs spec", "what's untested", "coverage report", "스펙 커버리지", "테스트 커버리지", "안 테스트된 거 뭐야". Produces specs/COVERAGE.md. Never modifies existing tests or specs.
gen-tests
/gen-tests
Generate test stubs from the existing specs/ directory and record whether they are active todos or inactive planning stubs. Use when the user wants to turn the spec into planned executable coverage for domain invariants, backend endpoints, and e2e flows. Triggers include "gen tests", "generate tests from spec", "spec to tests", "build test stubs", "테스트 생성", "스펙 기반 테스트". Detects the project's existing test framework. Writes stubs only — never overwrites existing tests. Asks the user for confirmation if more than 20 stubs would be created.
generate
/generate
Generate end-to-end specification markdown files that mirror the current implementation as a safety net. Use when the user wants to extract, document, or snapshot the app's behavior — across frontend action flows, backend use cases, queries, and domain features. Triggers include "generate spec", "spec mirror", "e2e spec", "document app", "mirror implementation", "스펙 생성", "스펙 미러", "구현 스펙 만들어줘", "전체 스펙 정리". Produces layered specs (frontend / backend / domain) plus flow specs that cross-reference layers. Asks the user for a brief architecture confirmation after its own analysis, before writing files.
lint
/lint
Audit the specs/ directory for internal hygiene issues — dead cross-references, missing source lines, stale [INFERENCE] markers, orphaned KEEP blocks, broken refs/ links. Use when the user wants to verify the spec itself is healthy, after manual edits to spec files, or before relying on the spec as a safety net. Triggers include "lint spec", "spec hygiene", "spec audit", "check spec health", "스펙 린트", "스펙 점검", "스펙 정합성". Produces specs/LINT.md and never modifies any other file. Different from compare (which checks spec vs code) — lint checks spec vs spec.
Stats
Version0.3.0
LanguageJavaScript
Stars1
MaintenanceGood
Last Commit
Added
Available In
Tags
Categories
