eval-speckit-extension

Solid

Evaluate the speckit-extension end-to-end against a real spec — verify lifecycle hooks fired, .spec-context.json captured each step into canonical history[], timing is real (not backfilled), and per-task execution was journaled. Umbrella eval for the spec-kit-side extension; grows as features land (auto-mode, etc.). Use when the user says "/eval-speckit-extension", "verify the extension worked", "did the hooks fire", "check the capture", or just ran a /speckit.* spec and wants it validated.

Testing & QA 90 stars 23 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
65
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Eval: speckit-extension The regression net for the `speckit-extension` (the spec-kit-side half of SpecKit Companion). It verifies the assumptions behind each feature against a **real spec the user created**, combining a deterministic file checker with a conversational cross-check of what the user actually did this session. Re-run it whenever a lifecycle/auto-mode/future feature ships. Eval areas (add a section per feature as the extension grows): 1. **Lifecycle capture** (shipped) — hooks → `write-context.py` → canonical `history[]`; per-task journaling; derive-from-files fallback. 2. **Command quality** (shipped) — `check_quality.py`: verbosity budgets on the spec artifacts, time-waste checks on `history[]` (untrusted spans, bursts, outliers), static prompting checks on the command-body sources. 3. _Auto-mode_ (future) — add checks here when it lands. 4. _…_ ## Steps ### 1. Resolve the target spec - If the user named a spec (`NNN` or a dir), use `specs/<that>/`. - Else pick the spec the user most recently created/ran in **this conversation** (whose `/speckit.*` or `/sdd:*` commands appear above). Fall back to the most recently modified `specs/*/` containing `.spec-context.json`. ### 2. Run the deterministic checker ```bash python3 apps/speckit-extension/scripts/check_capture.py specs/<NNN>-<slug>/ ``` Read the PASS/FAIL/INFO rows and the timing breakdown. (`--json` for machine output; `--strict` to exit non-zero on any FAIL.) ### 2b. Run the command-quality checke...

Details

Author
alfredoperez
Repository
alfredoperez/speckit-companion
Created
9 months ago
Last Updated
4 days ago
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category