codex-issue-plan-execute
npx skills add https://github.com/catlog22/claude-code-workflow --skill codex-issue-plan-execute
Agent 安装分布
Skill 文档
Codex Issue Plan-Execute Workflow
Streamlined autonomous workflow for Codex that integrates issue planning, queue management, and solution execution in a single stateful Skill. Supports batch processing with minimal queue overhead and dual-agent execution strategy.
Architecture Overview
For complete architecture details, system diagrams, and design principles, see ARCHITECTURE.md.
Key concepts:
- Persistent Dual-Agent System: Two long-running agents (Planning + Execution) that maintain context across all tasks
- Sequential Pipeline: Issues â Planning Agent â Solutions â Execution Agent â Results
- Unified Results: All results accumulated in single
planning-results.jsonandexecution-results.jsonfiles - Efficient Communication: Uses
send_input()for task routing without agent recreation overhead
â ï¸ Mandatory Prerequisites (强å¶åç½®æ¡ä»¶)
â ç¦æ¢è·³è¿: 卿§è¡ä»»ä½æä½ä¹åï¼å¿ é¡»é 读以ä¸ä¸¤ä»½P0è§èææ¡£ãæªçè§£è§èç´æ¥æ§è¡å°å¯¼è´è¾åºè´¨éä¸ç¬¦åæ åã
| Document | Purpose | When |
|---|---|---|
| specs/issue-handling.md | Issue å¤çè§èåæ°æ®ç»æ | æ§è¡åå¿ è¯» |
| specs/solution-schema.md | è§£å³æ¹æ¡æ°æ®ç»æåéªè¯è§å | æ§è¡åå¿ è¯» |
Execution Flow
Phase 1: Initialize Persistent Agents
â æ¥é
: ARCHITECTURE.md – ç³»ç»æ¶æ
â æ¥é
: phases/orchestrator.md – ç¼æé»è¾
â Spawn Planning Agent with prompts/planning-agent.md (stays alive)
â Spawn Execution Agent with prompts/execution-agent.md (stays alive)
Phase 2: Planning Pipeline
â æ¥é : phases/actions/action-plan.md, specs/subagent-roles.md For each issue sequentially:
- Send issue to Planning Agent via
send_input()with planning request - Wait for Planning Agent to return solution JSON
- Store result in unified
planning-results.jsonarray - Continue to next issue (agent stays alive)
Phase 3: Execution Pipeline
â æ¥é : phases/actions/action-execute.md, specs/quality-standards.md For each successful planning result sequentially:
- Send solution to Execution Agent via
send_input()with execution request - Wait for Execution Agent to complete implementation and testing
- Store result in unified
execution-results.jsonarray - Continue to next solution (agent stays alive)
Phase 4: Finalize
â æ¥é : phases/actions/action-complete.md â Close Planning Agent (after all issues planned) â Close Execution Agent (after all solutions executed) â Generate final report with statistics
State Schema
{
"status": "pending|running|completed",
"phase": "init|listing|planning|executing|complete",
"issues": {
"{issue_id}": {
"id": "ISS-xxx",
"status": "registered|planning|planned|executing|completed",
"solution_id": "SOL-xxx-1",
"planned_at": "ISO-8601",
"executed_at": "ISO-8601"
}
},
"queue": [
{
"item_id": "S-1",
"issue_id": "ISS-xxx",
"solution_id": "SOL-xxx-1",
"status": "pending|executing|completed"
}
],
"context": {
"work_dir": ".workflow/.scratchpad/...",
"total_issues": 0,
"completed_count": 0,
"failed_count": 0
},
"errors": []
}
Directory Setup
const timestamp = new Date().toISOString().slice(0,19).replace(/[-:T]/g, '');
const workDir = `.workflow/.scratchpad/codex-issue-${timestamp}`;
Bash(`mkdir -p "${workDir}"`);
Bash(`mkdir -p "${workDir}/solutions"`);
Bash(`mkdir -p "${workDir}/snapshots"`);
Output Structure
.workflow/.scratchpad/codex-issue-{timestamp}/
âââ planning-results.json # All planning results in single file
â âââ phase: "planning"
â âââ created_at: "ISO-8601"
â âââ results: [
â { issue_id, solution_id, status, solution, planned_at }
â ]
âââ execution-results.json # All execution results in single file
â âââ phase: "execution"
â âââ created_at: "ISO-8601"
â âââ results: [
â { issue_id, solution_id, status, commit_hash, files_modified, executed_at }
â ]
âââ final-report.md # Summary statistics and report
Reference Documents by Phase
ð§ Setup & Understanding (åå§åé¶æ®µ)
ç¨äºçè§£æ´ä¸ªç³»ç»æ¶æåæ§è¡æµç¨
| Document | Purpose | Key Topics |
|---|---|---|
| phases/orchestrator.md | ç¼æå¨æ ¸å¿é»è¾ | å¦ä½ç®¡çagentsãpipelineæµç¨ãç¶æè½¬æ¢ |
| phases/state-schema.md | ç¶æç»æå®ä¹ | 宿´ç¶ææ¨¡åãéªè¯è§åãæä¹ å |
| specs/agent-roles.md | Agentè§è²åèè´£å®ä¹ | Planning & Execution Agent详ç»è¯´æ |
ð Planning Phase (è§åé¶æ®µ)
æ§è¡Phase 2æ¶æ¥é – Planningé»è¾åIssueå¤ç
| Document | Purpose | When to Use |
|---|---|---|
| phases/actions/action-plan.md | Planningæµç¨è¯¦è§£ | çè§£issueâsolution转æ¢é»è¾ |
| phases/actions/action-list.md | Issueå表å¤ç | å¦ä¹ issueå è½½åå举é»è¾ |
| specs/issue-handling.md | Issueæ°æ®è§è | çè§£issueç»æåéªè¯è§å â å¿ è¯» |
| specs/solution-schema.md | è§£å³æ¹æ¡æ°æ®ç»æ | äºè§£solution JSONæ ¼å¼ â å¿ è¯» |
âï¸ Execution Phase (æ§è¡é¶æ®µ)
æ§è¡Phase 3æ¶æ¥é – å®ç°åéªè¯é»è¾
| Document | Purpose | When to Use |
|---|---|---|
| phases/actions/action-execute.md | Executionæµç¨è¯¦è§£ | çè§£solutionâimplementationé»è¾ |
| specs/quality-standards.md | è´¨éæ ååéªæ¶æ¡ä»¶ | æ£æ¥implementationæ¯å¦è¾¾æ |
ð Completion Phase (宿鶿®µ)
æ§è¡Phase 4æ¶æ¥é – æ¶å°¾åæ¥åé»è¾
| Document | Purpose | When to Use |
|---|---|---|
| phases/actions/action-complete.md | 宿æµç¨ | çææç»æ¥åãç»è®¡ä¿¡æ¯ |
ð Debugging & Troubleshooting (é®é¢ææ¥)
éå°é®é¢æ¶æ¥é – å¿«éå®ä½åè§£å³
| Issue | Solution Document |
|---|---|
| æ§è¡è¿ç¨ä¸ç¶æå¼å¸¸ | phases/state-schema.md – éªè¯ç¶æç»æ |
| Planning Agentè¾åºä¸ç¬¦å颿 | phases/actions/action-plan.md + specs/solution-schema.md |
| Execution Agentå®ç°å¤±è´¥ | phases/actions/action-execute.md + specs/quality-standards.md |
| Issueæ°æ®æ ¼å¼é误 | specs/issue-handling.md |
ð Architecture & Agent Definitions (æ¶æåAgentå®ä¹)
æ ¸å¿è®¾è®¡ææ¡£
| Document | Purpose | Notes |
|---|---|---|
| ARCHITECTURE.md | ç³»ç»æ¶æå设计åå | å¯å¨åå¿ è¯» |
| specs/agent-roles.md | Agentè§è²å®ä¹ | Planning & Execution Agent详ç»èè´£ |
| prompts/planning-agent.md | Planning Agentç»ä¸æç¤ºè¯ | ç¨äºåå§åPlanning Agent |
| prompts/execution-agent.md | Execution Agentç»ä¸æç¤ºè¯ | ç¨äºåå§åExecution Agent |
Usage Examples
Batch Process Specific Issues
codex -p "@.codex/prompts/codex-issue-plan-execute ISS-001,ISS-002,ISS-003"
Interactive Selection
codex -p "@.codex/prompts/codex-issue-plan-execute"
# Then select issues from the list
Resume from Snapshot
codex -p "@.codex/prompts/codex-issue-plan-execute --resume snapshot-path"
Skill Version: 1.0 Execution Mode: Autonomous Status: Ready for Customization