# PlanGate: A Gated Workflow Framework for AI Programming Agents

> A gated workflow for AI coding agents targeting production-level development, which structurally manages the complete development process from requirements to delivery through the core mechanism of "no implementation without approved plans".

- 板块: [Openclaw Llm](https://www.zingnex.cn/en/forum/board/openclaw-llm)
- 发布时间: 2026-04-23T21:44:38.000Z
- 最近活动: 2026-04-23T21:50:53.722Z
- 热度: 154.9
- 关键词: AI编程, 工作流, 门控机制, Claude Code, Codex CLI, 计划先行, 代码审查, 状态持久化, 开发Harness, 生产级AI
- 页面链接: https://www.zingnex.cn/en/forum/thread/plangate-ai
- Canonical: https://www.zingnex.cn/forum/thread/plangate-ai
- Markdown 来源: floors_fallback

---

## PlanGate: Introduction to the Gated Workflow Framework for AI Programming Agents

PlanGate is a gated workflow framework for AI coding agents targeting production-level development. Its core mechanism is "no implementation without approved plans", aiming to structurally manage the complete development process from requirements to delivery, and solve key issues in AI coding such as disconnect between planning and implementation, ambiguous approval boundaries, and post-hoc verification.

## Background of PlanGate's Birth

The popularity of AI coding tools has improved development efficiency, but also exposed new risks: AI implementations often outpace plans, approval and responsibility boundaries are ambiguous, verification becomes a post-hoc remedy, context and evaluation standards rely excessively on conversations or personal memory, and completion criteria are scattered across PRs and dialogue records. PlanGate was born to address this, placing AI within a development constraint harness with clear approval boundaries, explicit deliverables, and standard verification processes.

## Core Philosophy and Key Features of PlanGate

PlanGate's core design philosophy is "AI cannot write a single line of code without an approved plan". Its differences from traditional Harness engineering include:
- Plan-first: Never start implementation before approval
- Clear boundaries: Clearly define the boundaries for approval, rejection, and re-execution
- Deliverable retention: Retain plans, tasks, and test perspectives as deliverables
- Embedded verification: Must conduct acceptance checks, reviews, and handoffs after implementation
- Knowledge solidification: Fix judgment criteria and context in files instead of relying on personal memory.

## Detailed Explanation of PlanGate's Gated Architecture

PlanGate uses a multi-level gated mechanism:
- **C-3 Gate**: Human reviewers approve the AI-generated plan; only after approval can the AI enter the implementation phase
- **C-4 Gate**: After implementation, the code must pass PR review
- **Verification Levels**: L-0 (AI self-verification), V-1 to V-4 (a multi-level verification system from basic functional testing to integration testing).

## PlanGate's Workflow and State Persistence

### Workflow Structure
1. Job context creation: Each task has an independent directory `docs/working/TASK-XXXX/`
2. Plan generation and review: AI generates plans, todos, and test cases based on PBI, followed by self-review or external AI review
3. Human review and gated execution: AI gains execution permission after human approval of the plan.

### State Persistence
Transfer state to the file system; the task directory includes `plan.md` (plan), `review.md` (review records), `verification.md` (verification results), and `handoff.md` (handoff documents), bringing benefits such as auditability, recoverability, collaboration, and knowledge accumulation.

## v7 Hybrid Architecture and Multi-Tool Support

### v7 Hybrid Architecture
Introduces three-layer separation of Workflow, Skill, and Agent:
- Workflow layer: Defines process orchestration and gated rules
- Skill layer: Encapsulates reusable capability units
- Agent layer: Executes specific task agent instances

### Multi-Tool Support
Supports the combined use of Claude Code and Codex CLI:
| Tool | Entry File | Dedicated Configuration |
|------|------------|-------------------------|
| Claude Code | CLAUDE.md | .claude/ |
| Codex CLI | AGENTS.md | .codex/ |
| Shared | docs/ai/project-rules.md | docs/, scripts/ |

## Adoption Recommendations and Summary of PlanGate

### Adoption Recommendations
Progressive strategy:
1. Phase 1: Use C-3 plan approval in pilot projects
2. Phase 2: Introduce verification levels and state persistence
3. Phase 3: Expand to multiple projects and establish a shared Skill library
4. Phase 4: Adopt the complete v7 architecture

### Summary
PlanGate is an attempt to evolve AI-assisted development from "personal tools" to "team collaboration frameworks". It solves core issues through gated mechanisms, state persistence, and multi-level verification, allowing teams to enjoy AI efficiency while maintaining control and confidence in the development process.