From 7517f4f8ecacb6d2740ef5b3ec2b842799432292 Mon Sep 17 00:00:00 2001 From: catlog22 Date: Sun, 23 Nov 2025 13:44:02 +0800 Subject: [PATCH] docs: clarify manifest.json location in plan.md Phase 1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add explicit note in Phase 1 validation to prevent main Claude from incorrectly looking for manifest.json in .workflow/active/WFS-xxx/. manifest.json only exists in .workflow/archives/ (for archived sessions). Active sessions only have workflow-session.json (metadata). This prevents confusion during plan execution before agent invocation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .claude/commands/workflow/plan.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.claude/commands/workflow/plan.md b/.claude/commands/workflow/plan.md index 0059c1b6..96730e64 100644 --- a/.claude/commands/workflow/plan.md +++ b/.claude/commands/workflow/plan.md @@ -72,6 +72,8 @@ CONTEXT: Existing user database schema, REST API endpoints - Session ID successfully extracted - Session directory `.workflow/active/[sessionId]/` exists +**Note**: Session directory contains `workflow-session.json` (metadata). Do NOT look for `manifest.json` here - it only exists in `.workflow/archives/` for archived sessions. + **TodoWrite**: Mark phase 1 completed, phase 2 in_progress **After Phase 1**: Return to user showing Phase 1 results, then auto-continue to Phase 2