chevp-ai-framework

Record a human approval/acceptance for an artifact (ADR, CTX, EXP, PRD) in its provenance frontmatter.

Enter Context mode — read, verify, ask. No code changes allowed.

Promote a Plan Proposal (PROP-NNN) to a real CTX/EXP/PRD plan in its suggested chapter.

Enter Exploration mode — plan, design, prototype. No production code.

Validate a quality gate (G1, G2, or G3) against required deliverables.

> Many small reviewers. One orchestrator. Friction lives in the AI, not in the human.

Reviews plans, code changes, and ADRs against the project's architecture invariants. Use when a plan proposes a new pattern/layer, when changes cross architectural boundaries, or when a new ADR is drafted. Flags invariant violations.

Dispatcher kept for backward compatibility. Routes /gate-check requests to gatekeeper-g1 / gatekeeper-g2 / gatekeeper-g3. New code should invoke the specialised gatekeepers directly.

Validates the Context → Exploration transition (G1) of chevp-ai-framework. Use PROACTIVELY before any move from Context to Exploration and whenever /gate-check G1 is invoked. Returns a verdict (pass | block | conditional-pass), findings, and proposes Plan Proposals for out-of-scope items found in the CTX plan.

Validates the Exploration → Production transition (G2) of chevp-ai-framework. Use PROACTIVELY before any move from Exploration to Production and whenever /gate-check G2 is invoked. Returns a verdict (pass | block | conditional-pass), findings, and proposes Plan Proposals for out-of-scope items found in the EXP plan.

Use when the user wants to record an architecture decision, says "write an ADR", "new ADR", "document this decision", or when a non-trivial architectural choice is made during Context or Exploration that future contributors need to understand.

Use when the user starts a new task and a Context-Plan (CTX) is needed, or when they say "context plan", "CTX", "start context step", or a new request arrives with no active plan. Produces a CTX plan per the chevp-ai-framework template.

Use when a feature needs to be planned/designed in the Exploration step, or when the user says "EXP plan", "feature plan", "exploration plan", "design the feature". Produces an EXP plan/spec per chevp-ai-framework templates.

Use when an approved EXP plan is ready to be implemented and a Production-Plan (PRD) is needed, or when the user says "PRD plan", "production plan", "produce", "implement EXP-NNN", "draft PRD". Produces a PRD per the chevp-ai-framework template.

Use when an out-of-scope item, Challenger-identified failure mode, or NOT-in-Scope row warrants its own future plan (Rule 12). Trigger phrases: "create proposal", "PROP for this", "open a proposal", "log this for later", "this is out of scope but worth tracking". Produces a `PROP-NNN` file per the plan-proposal template.

3 hooks across 2 events