GSE-One — AI engineering companion for structured SDLC management
Command Claude Code
Post-audit fix session for the GSE-One methodology repository. Consumes the canonical registry LOCAL/audit/audit.json produced by /gse-meta-audit: verifies findings against LLM fabrication (per-cluster verification pass), persists verdicts in place, applies CONFIRMED fixes cluster by cluster, and closes with the full…
Command Claude Code
Audit the GSE-One methodology repository for coherence (Categories A-D), strategic quality (Category E), and distribution hygiene (Category F). Orchestrates the Python deterministic engine (audit.py, including the 5 Category F distribution jobs) + 23 parallel LLM sub-agents — 28 jobs total, defined in…
Command Claude Code
Run the mandatory GSE-One build pipeline for a commit to main: VERSION bump, CHANGELOG entry, generator --verify, add, commit, push, and the vX.Y.Z tag that triggers the release workflow. Thin executable checklist over CLAUDE.md > Critical rules > Build pipeline (canonical).
Command
Select backlog items for sprint, create/update sprint plan in .gse/plan.yaml. Cross-cutting — callable at any abstraction level.
Command
Simulate planned artefacts before production. Triggered by /gse:preview.
Command
Execute production plan in isolated worktree. Creates feature branch + worktree per task. Triggered by /gse:produce.
Command
Define functional and non-functional requirements. Triggered by /gse:reqs.
Command
Reload checkpoint, verify worktrees, brief user. Triggered by /gse:resume.
Command
Review all artefacts in current sprint. Operates on branch diff. Includes devil's advocate (P16). Triggered by /gse:review.
Command
Show lifecycle status, sprint state, artefact inventory, health, git state. Triggered by /gse:status.
Command
Execute a task outside standard lifecycle. Triggered by /gse:task.
Command
Define test strategy, set up environment, write tests, execute campaigns, produce evidence. Triggered by /gse:tests.
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: