Permissions

Flow-Next does not replace team ownership. It makes ownership explicit.

Humans own

• Product intent
• Scope decisions
• Risk tolerance
• Merge decisions
• Production responsibility

Agents delegate

• Codebase search
• Draft specs
• Task decomposition
• Implementation
• Initial review
• PR comment resolution

Reviewers validate

Review the handover object first, then the diff. The PR body should point you to acceptance coverage, critical changes, decisions, open items, and where to look.

Agent permissions

Give agents enough access to inspect, edit, test, and document the work, but keep destructive actions explicit:

Permission area	Default stance
Read repo files	Allow
Edit scoped project files	Allow during /flow-next:work
Run tests and linters	Allow
Install new dependencies	Require human review
Push branches	Allow only when requested by team convention
Merge PRs	Human-owned
Delete state or reset git	Require explicit human approval

The exact policy depends on host harness, but the ownership model should be consistent across Claude Code, Codex, and Droid.

Review gates as policy

For production teams, make the gates explicit:

• Plan review before implementation for risky specs.
• Implementation review before PR.
• Completion review before closing the spec.
• Human approval before merge.
• Changelog and docs update when behavior changes.

flowchart LR
  Spec["Spec"] --> PlanReview["Plan review"]
  PlanReview --> Work["Work"]
  Work --> ImplReview["Implementation review"]
  ImplReview --> Completion["Completion review"]
  Completion --> Human["Human merge decision"]

Sensitive work

Use tighter review for:

• authentication and authorization
• billing and entitlements
• migrations and data deletion
• public APIs and config formats
• plugin install/update behavior
• autonomous execution hooks

For these, prefer spec-as-PR and require a human to review the spec before /flow-next:work starts.