From 9cb9b2213b095bd6c26fbbe223d75dd9fedbc8bb Mon Sep 17 00:00:00 2001
From: catlog22 <catlog22@github.com>
Date: Mon, 17 Nov 2025 20:58:51 +0800
Subject: [PATCH] fix(lite-plan): correct executionContext.planObject.tasks
 type documentation

Issue found by Gemini analysis:
- executionContext.planObject.tasks was incorrectly documented as string[]
- Actual runtime structure is array of structured task objects (7 fields)
- This caused documentation mismatch between lite-plan and lite-execute

Fix:
- Update executionContext definition to show full task object structure
- Add comment clarifying it's an array of structured objects (7 fields each)
- Aligns with actual implementation and lite-execute consumption logic

Impact: Documentation only (no code changes, runtime behavior was already correct)
---
 .claude/commands/workflow/lite-plan.md | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/.claude/commands/workflow/lite-plan.md b/.claude/commands/workflow/lite-plan.md
index 3f3a73f8..ea4e2ef1 100644
--- a/.claude/commands/workflow/lite-plan.md
+++ b/.claude/commands/workflow/lite-plan.md
@@ -100,10 +100,24 @@ Context passed to lite-execute via --in-memory (Phase 5):
 
 ```javascript
 {
-  planObject: {                        // See planObject structure above
+  planObject: {                        // Complete planObject structure (see above)
     summary: string,
     approach: string,
-    tasks: string[],
+    tasks: [                           // Array of structured task objects (7 fields each)
+      {
+        title: string,
+        file: string,
+        action: string,
+        description: string,
+        implementation: string[],
+        reference: {
+          pattern: string,
+          files: string[],
+          examples: string
+        },
+        acceptance: string[]
+      }
+    ],
     estimated_time: string,
     recommended_execution: string,
     complexity: string