Bang-isme

Use for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.

The English summary is being prepared. Showing the original description.

Use when asking project status, next priority, sprint health, blockers, deadlines, risk register, or daily brief generation.

The English summary is being prepared. Showing the original description.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup

The English summary is being prepared. Showing the original description.

Use before build, fix, debug, review, or docs implementation; converts prompts into structured intent JSON with goal, constraints, and routing.

The English summary is being prepared. Showing the original description.

Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.

The English summary is being prepared. Showing the original description.

Use for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes.

The English summary is being prepared. Showing the original description.

Use when implementation needs isolation from the current workspace; creates git worktrees with safe directory selection and baseline verification.

The English summary is being prepared. Showing the original description.

Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.

The English summary is being prepared. Showing the original description.