claude-code-workflow 6.3.17 → 6.3.19

package/.codex/prompts/issue-queue.md

@@ -1,6 +1,6 @@
 ---
 description: Form execution queue from bound solutions (orders solutions, detects conflicts, assigns groups)
-argument-hint: "[--issue <id>]"
+argument-hint: "[--issue <id>] [--append <id>]"
 ---
 
 # Issue Queue (Codex Version)
@@ -11,10 +11,32 @@ Create an ordered execution queue from all bound solutions. Analyze inter-soluti
 
 This workflow is **ordering only** (no execution): it reads bound solutions, detects conflicts, and produces a queue file that `issue-execute.md` can consume.
 
+**Design Principle**: Queue items are **solutions**, not individual tasks. Each executor receives a complete solution with all its tasks.
+
+## Core Guidelines
+
+**⚠️ Data Access Principle**: Issues and queue files can grow very large. To avoid context overflow:
+
+| Operation | Correct | Incorrect |
+|-----------|---------|-----------|
+| List issues (brief) | `ccw issue list --status planned --brief` | `Read('issues.jsonl')` |
+| List queue (brief) | `ccw issue queue --brief` | `Read('queues/*.json')` |
+| Read issue details | `ccw issue status <id> --json` | `Read('issues.jsonl')` |
+| Get next item | `ccw issue next --json` | `Read('queues/*.json')` |
+| Update status | `ccw issue update <id> --status ...` | Direct file edit |
+| Sync from queue | `ccw issue update --from-queue` | Direct file edit |
+
+**Output Options**:
+- `--brief`: JSON with minimal fields (id, status, counts)
+- `--json`: Full JSON (for detailed processing)
+
+**ALWAYS** use CLI commands for CRUD operations. **NEVER** read entire `issues.jsonl` or `queues/*.json` directly.
+
 ## Inputs
 
 - **All planned**: Default behavior → queue all issues with `planned` status and bound solutions
 - **Specific issue**: `--issue <id>` → queue only that issue's solution
+- **Append mode**: `--append <id>` → append issue to active queue (don't create new)
 
 ## Output Requirements
 
@@ -161,10 +183,12 @@ Group assignment:
 ```json
 {
   "active_queue_id": "QUE-20251228-120000",
+  "active_queue_ids": ["QUE-20251228-120000"],
   "queues": [
     {
       "id": "QUE-20251228-120000",
       "status": "active",
+      "priority": 1,
       "issue_ids": ["ISS-001", "ISS-002"],
       "total_solutions": 3,
       "completed_solutions": 0,
@@ -174,20 +198,49 @@ Group assignment:
 }
 ```
 
+## Multi-Queue Management
+
+Multiple queues can be active simultaneously. The system executes queues in priority order (lower = higher priority).
+
+**Activate multiple queues:**
+```bash
+ccw issue queue activate QUE-001,QUE-002,QUE-003
+```
+
+**Set queue priority:**
+```bash
+ccw issue queue priority QUE-001 --priority 1
+ccw issue queue priority QUE-002 --priority 2
+```
+
+**Execution behavior with multi-queue:**
+- `ccw issue next` automatically selects from active queues in priority order
+- Complete all items in Q1 before moving to Q2 (serialized execution)
+- Use `--queue QUE-xxx` to target a specific queue
+
 ### Step 7: Update Issue Statuses
 
-For each queued issue, update status to `queued`:
+**MUST use CLI command** (NOT direct file operations):
 
 ```bash
+# Option 1: Batch update from queue (recommended)
+ccw issue update --from-queue              # Use active queue
+ccw issue update --from-queue QUE-xxx      # Use specific queue
+
+# Option 2: Individual issue update
 ccw issue update <issue-id> --status queued
 ```
 
+**⚠️ IMPORTANT**: Do NOT directly modify `issues.jsonl`. Always use CLI command to ensure proper validation and history tracking.
+
 ## Queue Item ID Format
 
 - Solution items: `S-1`, `S-2`, `S-3`, ...
 - Sequential numbering starting from 1
 
-## Done Criteria
+## Quality Checklist
+
+Before completing, verify:
 
 - [ ] Exactly 2 files generated: queue JSON + index update
 - [ ] Queue has valid DAG (no circular dependencies)
@@ -212,6 +265,16 @@ ccw issue update <issue-id> --status queued
 | Circular dependency detected | Abort, report cycle details |
 | Missing solution file | Skip issue, log warning |
 | Index file missing | Create new index |
+| Index not updated | Auto-fix: Set active_queue_id to new queue |
+
+## Done Criteria
+
+- [ ] All planned issues with `bound_solution_id` are included
+- [ ] Queue JSON written to `queues/{queue-id}.json`
+- [ ] Index updated in `queues/index.json` with `active_queue_id`
+- [ ] No circular dependencies in solution DAG
+- [ ] Parallel groups have no file overlaps
+- [ ] Issue statuses updated to `queued`
 
 ## Start Execution
 
@@ -222,3 +285,4 @@ ccw issue list --status planned --json
 ```
 
 Then follow the workflow to generate the queue.
+

package/.codex/prompts/lite-execute.md

@@ -63,22 +63,29 @@ For current task, perform:
 ```markdown
 ## Executing: [task.title]
 
-**Target**: `[task.file]`
+**Scope**: `[task.scope]` (module/feature level)
 **Action**: [task.action]
 
+### Modification Points
+For each point in task.modification_points:
+- **File**: [point.file]
+- **Target**: [point.target] (function/class/line range)
+- **Change**: [point.change]
+
 ### Implementation
 [Follow task.implementation steps]
 
 ### Reference Pattern
 - Pattern: [task.reference.pattern]
-- Examples: [task.reference.files]
+- Files: [task.reference.files]
+- Examples: [task.reference.examples]
 
 ### Acceptance Criteria
 - [ ] [criterion 1]
 - [ ] [criterion 2]
 ```
 
-**Execute all implementation steps. Verify all acceptance criteria.**
+**Execute all modification points. Verify all acceptance criteria.**
 
 ### Step 4: Mark Completed
 
@@ -104,22 +111,40 @@ Output progress:
 
 ```json
 {
-  "id": "task-1",
-  "title": "Task Title",
-  "file": "path/to/file.ts",
-  "action": "create|modify|refactor",
-  "description": "What to do",
-  "implementation": ["step 1", "step 2"],
+  "id": "T1",
+  "title": "Implement auth validation",
+  "scope": "src/auth/",
+  "action": "Create|Update|Implement|Refactor|Add|Delete|Configure|Test|Fix",
+  "description": "What to implement (1-2 sentences)",
+  "modification_points": [
+    {
+      "file": "src/auth/validator.ts",
+      "target": "validateToken:45-60",
+      "change": "Add expiry check"
+    },
+    {
+      "file": "src/auth/middleware.ts",
+      "target": "authMiddleware",
+      "change": "Call new validator"
+    }
+  ],
+  "implementation": ["step 1", "step 2", "...max 7 steps"],
   "reference": {
     "pattern": "pattern name",
-    "files": ["example1.ts", "example2.ts"]
+    "files": ["example1.ts"],
+    "examples": "specific guidance"
   },
   "acceptance": ["criterion 1", "criterion 2"],
-  "depends_on": ["task-0"],
+  "depends_on": ["T0"],
   "status": "pending|completed"
 }
 ```
 
+**Key Fields**:
+- `scope`: Module/feature level path (prefer over single file)
+- `modification_points[]`: All files to modify with precise targets
+- `target`: Function/class/line range (e.g., `validateToken:45-60`)
+
 ## Execution Rules
 
 1. **Never stop mid-workflow** - Continue until all tasks complete