feat: implement feature-driven artifact architecture for brainstorm-plan-execute pipeline

Restructure brainstorm artifacts from role-dimension to feature-dimension
to eliminate information loss at the brainstorm→plan boundary. Key changes:

- artifacts.md: Add Phase 4.5 Feature Decomposition in guidance-specification
- conceptual-planning-agent.md: Name sub-docs by feature (analysis-F-{id}-{slug}.md)
- role-analysis.md: Pass feature list to Phase 3 agent prompts
- synthesis.md: Add Phase 6 parallel feature spec generation + feature-index.json
- task-generate-agent.md: Inject feature-index.json path into agent prompts
- context-search-agent.md: Flatten brainstorm_artifacts structure (feature_index,
  feature_specs, cross_cutting_specs as top-level fields)
- action-planning-agent.md: Add feature-index driven on-demand loading, plan-time
  expansion for pre_analysis commands, fix cross_cutting_specs string array access
This commit is contained in:
catlog22
2026-02-11 16:32:30 +08:00
parent 8475a724ae
commit 5a4350beb4
7 changed files with 891 additions and 74 deletions

View File

@@ -279,6 +279,19 @@ Output:
Session ID: {session-id}
MCP Capabilities: {exa_code, exa_web, code_index}
## FEATURE SPECIFICATIONS (conditional)
If .workflow/active/{session-id}/.brainstorming/feature-specs/ exists:
Feature Index: .workflow/active/{session-id}/.brainstorming/feature-specs/feature-index.json
Feature Spec Dir: .workflow/active/{session-id}/.brainstorming/feature-specs/
Use feature-index.json to:
- Map features to implementation tasks (feature_id → task alignment)
- Reference individual feature spec files (spec_path) for detailed requirements
- Identify cross-cutting concerns (cross_cutting_specs) that span multiple tasks
- Align task priorities with feature priorities
If the directory does not exist, skip this section (backward compatible with non-brainstorm workflows).
## USER CONFIGURATION (from Phase 0)
Execution Method: ${userConfig.executionMethod} // agent|hybrid|cli
Preferred CLI Tool: ${userConfig.preferredCliTool} // codex|gemini|qwen|auto
@@ -461,6 +474,19 @@ Output:
Session ID: {session-id}
MCP Capabilities: {exa_code, exa_web, code_index}
## FEATURE SPECIFICATIONS (conditional)
If .workflow/active/{session-id}/.brainstorming/feature-specs/ exists:
Feature Index: .workflow/active/{session-id}/.brainstorming/feature-specs/feature-index.json
Feature Spec Dir: .workflow/active/{session-id}/.brainstorming/feature-specs/
Use feature-index.json to:
- Map features to module-scoped tasks (filter by ${module.paths.join(', ')})
- Reference individual feature spec files (spec_path) for detailed requirements
- Identify cross-cutting concerns affecting this module
- Align task priorities with feature priorities
If the directory does not exist, skip this section (backward compatible with non-brainstorm workflows).
## USER CONFIGURATION (from Phase 0)
Execution Method: ${userConfig.executionMethod} // agent|hybrid|cli
Preferred CLI Tool: ${userConfig.preferredCliTool} // codex|gemini|qwen|auto