agentic-governance

Deep enterprise brainstorming that turns vibe-coded ideas into Technical Design Documents. Four phases: EXTRACT (pull intent), DISCOVER (research codebase), PRODUCT DESIGN (user journeys, UI/UX, workflows, platform context), ENGINEER (full TDD). Thinks beyond technical solutions — designs the product, not just the code. Context-aware: auto-detects project type (Shopify app, SaaS, mobile, API, CLI) and applies platform-specific design thinking.

Use when a locked enterprise contract exists and implementation must proceed through strict TDD, contract traceability, and staged review handoffs

Use when verified enterprise work or a resolved debugging session should be captured as searchable institutional knowledge with prevention guidance

Use when an enterprise implementation plan exists and work needs a locked contract with postconditions, invariants, consumer mapping, and traceability before build starts

4-phase systematic debugging: investigate, blast radius scan, root cause identification, TDD fix. Finds root causes not symptoms. Blast radius scan catches sibling bugs. 3-fail circuit breaker prevents fix-forward loops. Use for any bug, test failure, or unexpected behavior.

Use when starting enterprise work in a new repo, new worktree, unfamiliar package, or new computer, or whenever commands, paths, conventions, portability, or project traps are not yet known

Use when reviewed enterprise work still needs adversarial probing, mechanical checks, and recycle-loop bug closure before final verification

Use when enterprise work has been built and reviewed and needs a final mechanical ship gate before merge, install, or release-level signoff

Use when an approved enterprise design exists and the next step is to turn it into an exact implementation plan with file paths, task boundaries, and verification commands

End-to-end PR conversation closer and advisory review harvester for enterprise work. Use this whenever the user mentions unresolved PR conversations, Copilot/GitHub review comments, a PR that cannot merge, skipped/non-blocking Copilot feedback, a failed PR review, or asks to address/resolve/learn from PR feedback. It supports blocking-closeout mode for merge blockers and advisory-harvest mode for valuable non-blocking comments, fixes real bugs with tests, verifies the current head, replies/resolves only where appropriate, and compounds learnings so the same review failure is caught earlier next time.

Use when enterprise implementation is complete enough for a structured review that separates spec compliance from code quality and classifies drift explicitly

Use when starting a feature, significant refactor, enterprise hardening effort, or multi-stage bugfix that needs end-to-end workflow control, portable repo-local artifacts, and explicit proof scope

Use when enterprise work is about to be declared complete and the claim needs fresh evidence, postcondition tracing, and an explicit proof-scope verdict

Execute one governed packet through Compound Engineering while preserving governance truth.

Execute one governed packet through GSD while preserving governance truth.

Execute one governed packet through Superpowers while preserving governance truth.

Portable governance layer for long-running AI coding work. Use when the challenge is keeping a whole program bounded, resumable, and evidence-backed across sessions and agents.

Build or refresh the objective map before packet execution. Use when the program truth needs to be defined from artifacts instead of memory.

Turn governed work into precise packets with owned surface, forbidden surface, prerequisites, and evidence expectations.

Run Ralph as a bounded packet executor inside governance.