1,440 tagged workflow, measured the same way as everything else here.
Browse within: experimental 902artifacts 429archive 190explore 150thinking 149specs 87redhat 68spec-driven-development 57verify 48learning 41onboarding 41tutorial 41bulk 40gemini 40
Command
Parallel multi-lens adversarial critique of a spec's test plan (the ## Test plan section), with a bounded revise loop that tightens it. Dispatches 6 test-design lenses, merges findings, optionally revises, reports a verdict. Report-only, never blocks /kit:execute.
Command
Derive a test-case coverage matrix from a spec's acceptance criteria before /kit:execute. Writes a ## Test plan section into the active spec. A coverage target across categories, not an exhaustive test list.
Command
Turn a SOLID-verdict ## Test plan critique into real, executing test code via kit:test-writer, one case per matrix row. Never dispatches against a missing, stale, or non-SOLID verdict.
Command
Challenge an idea before writing any spec. 6 forcing questions that reframe the product.
Command
Downstream UI-design loop: write a structured ## UI design brief, delegate generation to the external frontend-design skill, critique via /kit:visual-team, and auto-revise (bounded). Opt-in, downstream-facing; the kit ships no renderer.
Command
Re-run the test levels (task-verifier + integration-verifier + acceptance-verifier + system-verifier) on the current spec/branch read-only, no rebuild. The on-demand executor of the complete V-model right arm.
Command
Parallel multi-lens critique of a visual/UI design. Dispatches 5 design lenses, merges findings, reports a verdict. Report-only, downstream-facing (the kit itself has no UI).
Command
Plan a chunk of work too big for one agent session as a shared decision map: map.md + typed decision tickets in the mega-goal folder, resolved one per session through the kit's own grill/prototype/research machinery, until nothing is left to decide. Then hand off to /kit:spec or a ROADMAP, never straight to execute.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: