docs: Linear-spawned issue contract for Codex in AGENTS.md#6
Conversation
Codifies how Codex operates when delegated a Linear issue: the issue is the spec; a Codex-ready gate (acceptance criteria + named surface + validation) with ambiguity -> stop and comment; executor-not-orchestrator (cross-lane sequencing stays in .plans/status.json + the human); target the issue's integration branch; PR body links the issue (Closes PRD-NNN); never self-merge. Tailored to this repo's commands and existing sections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 46 minutes and 25 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds Codex-specific guidance for handling Linear-dispatched issues in AGENTS.md, defining how Linear issues should be treated as specs and how Codex should validate, scope, branch, and open PRs for delegated work.
Changes:
- Adds a new Linear-spawned issue contract for Codex.
- Defines readiness requirements, scoped execution expectations, PR linkage, and validation evidence.
- Connects Linear issue work to repo package surfaces and privacy constraints.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| Linear (workspace `greenpill-dev-guild`; teams Product `PRD` / Research `RESR`) is the durable backlog — never open GitHub Issues for backlog work. Codex work is labeled `agent:codex` (distinct from `agent:claude` interactive and `agent:routine` cron writes). The Linear MCP is wired into the Codex environment for read/query and state transitions. | ||
|
|
||
| When dispatched from a Linear issue, **that issue is your spec** — read it in full, plus this file and any `.plans/<feature>/` lane it references. |
Adds a consistent Linear-Spawned Issue Contract to
AGENTS.mdso Codex operates reliably when delegated a Linear issue — part of a 3-repo rollout (green-goods, network, coop).Core (same across all three):
.plans/<feature>lane it references.package:*+ validation; otherwise stop and comment, don't guess..plans/status.json+ the human.Closes PRD-NNN); never self-merge; contracts get extra review.Tailored per repo to its actual commands and existing structure — green-goods' Validation Ladder; coop's Planning-OS
*.codex.todo.mdlanes; network had no Linear/lane model before this.🤖 Generated with Claude Code