Menu
Pilot a community Spec Kit extension without pretending it is trusted, official, or a hard gate
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
Lock what an analytical financial redesign may beautify, but never hide, reorder, or distort
Test tripwires for mortgage analysis UI redesign — preserves logic integrity through visual changes
Choose Spec Kit extensions that reinforce real repo gaps without duplicating existing orchestration
Run Spec Kit through the repo-pinned official CLI and keep the official git extension as the branch workflow source of truth
Freeze cross-cutting contracts before parallel implementation starts
Design financial result flows that explain cost, quality, and provenance before persuasion
| name | community-spec-kit-pilot |
| description | Pilot a community Spec Kit extension without pretending it is trusted, official, or a hard gate |
| domain | developer-workflow, governance |
| confidence | high |
| source | earned (2026-04-24 batalla-ias ci-guard pilot) |
Sometimes a community Spec Kit extension fits a real repo gap, but the upstream package is not verified and may not even install cleanly against the pinned official CLI. In that case, do the boring thing: pin provenance, patch only what is required for compatibility, and keep the rollout advisory until the repo explicitly decides otherwise.
speckit:ci:setup-style entrypoint for the community pilot.fail_* settings to false until the team explicitly chooses a merge gate.