refactor: team-planex dual-version optimization with v5 architecture

Claude version: add coordinator role with Spawn-and-Stop beat model,
replace role-routed planner/executor with team-worker agents using
lightweight role-specs (~80-110 lines each).

Codex version: inline planning into main flow, remove planner agent,
spawn executors directly per issue without waiting.

Both versions preserve 3 input types (Issue IDs / --text / --plan).

.codex/skills/team-planex/agents/executor.md

@@ -23,13 +23,13 @@ completion report.
 
 | Action | Allowed |
 |--------|---------|
-| Read solution artifact from disk | ✅ |
-| Implement via Codex CLI | ✅ |
-| Run tests for verification | ✅ |
-| git commit completed work | ✅ |
-| Create or modify issues | ❌ |
-| Spawn subagents | ❌ |
-| Interact with user (AskUserQuestion) | ❌ |
+| Read solution artifact from disk | Yes |
+| Implement via Codex CLI | Yes |
+| Run tests for verification | Yes |
+| git commit completed work | Yes |
+| Create or modify issues | No |
+| Spawn subagents | No |
+| Interact with user (AskUserQuestion) | No |
 
 ---
 
@@ -38,7 +38,6 @@ completion report.
 ### Step 1: Load Context
 
 After reading role definition:
-- Run: `ccw spec load --category execution`
 - Extract issue ID, solution file path, session dir from task message
 
 ### Step 2: Load Solution
@@ -52,7 +51,7 @@ const solution = solutionData.solution
 
 If file not found or invalid:
 - Log error: `[executor] ERROR: Solution file not found: ${solutionFile}`
-- Output: `EXEC_FAILED:{issueId}:solution_file_missing`
+- Output: `EXEC_FAILED:${issueId}:solution_file_missing`
 - Stop execution
 
 Verify solution has required fields:
@@ -81,10 +80,9 @@ ${JSON.stringify(solution.bound, null, 2)}
 ## Implementation Requirements
 1. Follow the solution plan tasks in order
 2. Write clean, minimal code following existing patterns
-3. Read .workflow/specs/*.md for project conventions
-4. Run tests after each significant change
-5. Ensure all existing tests still pass
-6. Do NOT over-engineer - implement exactly what the solution specifies
+3. Run tests after each significant change
+4. Ensure all existing tests still pass
+5. Do NOT over-engineer - implement exactly what the solution specifies
 
 ## Quality Checklist
 - [ ] All solution tasks implemented
@@ -92,9 +90,6 @@ ${JSON.stringify(solution.bound, null, 2)}
 - [ ] Existing tests pass
 - [ ] New tests added where specified in solution
 - [ ] No security vulnerabilities introduced
-
-## Project Guidelines
-@.workflow/specs/*.md
 PROMPT_EOF
 )" --tool codex --mode write --id planex-${issueId}
 ```
@@ -120,7 +115,6 @@ if (testCmd) {
   const testResult = Bash(`${testCmd} 2>&1 || echo TEST_FAILED`)
 
   if (testResult.includes('TEST_FAILED') || testResult.includes('FAIL')) {
-    // Report failure with resume command
     const resumeCmd = `ccw cli -p "Fix failing tests" --resume planex-${issueId} --tool codex --mode write`
 
     Write({
@@ -179,7 +173,6 @@ EXEC_DONE:${issueId}
 If Codex CLI execution fails or times out:
 
 ```bash
-# Resume with same session ID
 ccw cli -p "Continue implementation from where stopped" \
   --resume planex-${issueId} \
   --tool codex --mode write \
@@ -194,19 +187,19 @@ Resume command is always logged to `${sessionDir}/errors.json` on any failure.
 
 | Scenario | Resolution |
 |----------|------------|
-| Solution file missing | Output `EXEC_FAILED:{id}:solution_file_missing`, stop |
-| Solution JSON malformed | Output `EXEC_FAILED:{id}:solution_invalid`, stop |
+| Solution file missing | Output `EXEC_FAILED:<id>:solution_file_missing`, stop |
+| Solution JSON malformed | Output `EXEC_FAILED:<id>:solution_invalid`, stop |
 | Issue status update fails | Log warning, continue |
-| Codex CLI failure | Log resume command to errors.json, output `EXEC_FAILED:{id}:codex_failed` |
-| Tests failing | Log test output + resume command, output `EXEC_FAILED:{id}:tests_failing` |
-| Commit fails | Log warning, still output `EXEC_DONE:{id}` (implementation complete) |
+| Codex CLI failure | Log resume command to errors.json, output `EXEC_FAILED:<id>:codex_failed` |
+| Tests failing | Log test output + resume command, output `EXEC_FAILED:<id>:tests_failing` |
+| Commit fails | Log warning, still output `EXEC_DONE:<id>` (implementation complete) |
 | No test command found | Skip test step, proceed to commit |
 
 ## Key Reminders
 
 **ALWAYS**:
-- Output `EXEC_DONE:{issueId}` on its own line when implementation succeeds
-- Output `EXEC_FAILED:{issueId}:{reason}` on its own line when implementation fails
+- Output `EXEC_DONE:<issueId>` on its own line when implementation succeeds
+- Output `EXEC_FAILED:<issueId>:<reason>` on its own line when implementation fails
 - Log resume command to errors.json on any failure
 - Use `[executor]` prefix in all status messages