diff --git a/.claude/agents/action-planning-agent.md b/.claude/agents/action-planning-agent.md index 87522a10..f2d12cab 100644 --- a/.claude/agents/action-planning-agent.md +++ b/.claude/agents/action-planning-agent.md @@ -67,7 +67,11 @@ You are a pure execution agent specialized in creating actionable implementation Commands: Read({{context_package_path}}) Output: Complete context package object -3. Load brainstorming artifacts (in priority order) +3. Check existing plan (if resuming) + - If IMPL_PLAN.md exists: Read for continuity + - If task JSONs exist: Load for context + +4. Load brainstorming artifacts (in priority order) a. guidance-specification.md (Highest Priority) → Overall design framework and architectural decisions b. Role analyses (progressive loading: load incrementally by priority) @@ -78,11 +82,11 @@ You are a pure execution agent specialized in creating actionable implementation d. Conflict resolution (if conflict_risk ≥ medium) → Review resolved conflicts in artifacts -4. Optional MCP enhancement +5. Optional MCP enhancement → mcp__exa__get_code_context_exa() for best practices → mcp__exa__web_search_exa() for external research -5. Assess task complexity (simple/medium/complex) +6. Assess task complexity (simple/medium/complex) ``` **Context Package Structure** (fields defined by context-search-agent): diff --git a/.claude/commands/workflow/tools/task-generate-agent.md b/.claude/commands/workflow/tools/task-generate-agent.md index c3a50766..9ee739cc 100644 --- a/.claude/commands/workflow/tools/task-generate-agent.md +++ b/.claude/commands/workflow/tools/task-generate-agent.md @@ -65,54 +65,7 @@ Generate implementation planning documents (IMPL_PLAN.md, task JSONs, TODO_LIST. IMPORTANT: This is PLANNING ONLY - you are generating planning documents, NOT implementing code. -CRITICAL: Use progressive loading due to analysis.md file size - -## MANDATORY FIRST STEPS -1. Read session metadata: {session.session_metadata_path} -2. Load context package STRUCTURE ONLY: {session.context_package_path} -3. Use PROGRESSIVE 4-phase loading strategy (detailed below) - -## PROGRESSIVE LOADING STRATEGY (4 Phases) - -### PHASE 1: Core Context (REQUIRED - Always Load First) -Purpose: Establish baseline understanding - -Step 1.1 - Session Metadata: - Read: {session.session_metadata_path} - Extract: User description, project scope, technical constraints - -Step 1.2 - Context Package Structure (catalog only): - Read: {session.context_package_path} - Extract: metadata, project_context, assets (PATHS only), brainstorm_artifacts (catalog), conflict_detection - -Step 1.3 - Existing Plan (if resuming): - Check: .workflow/active/{session-id}/IMPL_PLAN.md - Action: If exists, load for continuity - -### PHASE 2: Selective Artifacts (Load Smart) -Purpose: Get architectural guidance for task planning - -Loading strategy (choose based on availability): -- **If synthesis_output exists**: Load ONLY synthesis_output.path (already integrates all role perspectives) -- **If guidance_specification exists**: Load guidance first, then progressively load role analyses as needed -- **If only role analyses exist**: Progressively load role analyses by priority - -Default approach: Progressive loading - load artifacts incrementally, one at a time, to manage file size. - -Conflict handling: If conflict_risk≥medium, check conflict_detection.status for resolved conflicts - -### PHASE 3: Load More Analysis (if needed) -Continue loading additional role analysis.md files ONE at a time when current context lacks detail. -Reason: Each analysis.md is long; progressive loading prevents token overflow. - -### PHASE 4: Project Assets (FINAL) -Purpose: Get concrete project context - -Extract from context_package: - - focus_areas: Target directories - - assets.source_code: File PATHS (read content selectively) - - assets.documentation: Reference docs - - dependencies: Internal and external +CRITICAL: Follow the progressive loading strategy defined in agent specification (load analysis.md files incrementally due to file size) ## SESSION PATHS Input: