catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-13 02:41:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

Refactor workflow to replace synthesis-specification.md with role analysis documents

Browse Source 
- Updated references in various workflow commands to utilize role analysis documents instead of synthesis-specification.md.
- Modified CLI templates and command references to reflect the new architecture and document structure.
- Introduced conflict-resolution command to analyze and resolve conflicts between implementation plans and existing codebase.
- Deprecated synthesis role template and provided migration guidance for transitioning to the new role analysis approach.
This commit is contained in:
catlog22
2025-10-24 11:08:15 +08:00
parent ef187d3a4b
commit 57fa379e45
35 changed files with 1835 additions and 1271 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
.claude/workflows/cli-templates/planning-roles/synthesis-role.md
View File

@@ -1,4 +1,25 @@
# Synthesis Role Template
# ⚠️ DEPRECATED: Synthesis Role Template
## DEPRECATION NOTICE
**This template is DEPRECATED and no longer used.**
### Why Deprecated
The `/workflow:brainstorm:synthesis` command has been redesigned:
- **Old behavior**: Generated synthesis-specification.md consolidating all role analyses
- **New behavior**: Performs cross-role analysis, identifies ambiguities, interacts with user for clarification, and updates role analysis.md files directly
### Migration
- **Role analyses are the source of truth**: Each role's analysis.md file is updated directly
- **Planning reads role documents**: The planning phase dynamically reads all role analysis.md files
- **No template needed**: The clarification workflow doesn't require a document template
### Historical Context
This template was used to guide the generation of synthesis-specification.md from multiple role perspectives. It is preserved for historical reference but should not be used in the new architecture.
---
# Original Template (Historical Reference)
## Purpose
Generate comprehensive synthesis-specification.md that consolidates all role perspectives from brainstorming into actionable implementation specification.
@@ -18,7 +39,7 @@ Generate comprehensive synthesis-specification.md that consolidates all role per
```markdown
# [Topic] - Integrated Implementation Specification
**Framework Reference**: @topic-framework.md | **Generated**: [timestamp] | **Session**: WFS-[topic-slug]
**Framework Reference**: @guidance-specification.md | **Generated**: [timestamp] | **Session**: WFS-[topic-slug]
**Source Integration**: All brainstorming role perspectives consolidated
**Document Type**: Requirements & Design Specification (WHAT to build)
@@ -344,7 +365,7 @@ Document known constraints that affect planning:
### Cross-Role Synthesis Process
1. **Load All Role Analyses**: Read topic-framework.md and all discovered */analysis.md files
1. **Load All Role Analyses**: Read guidance-specification.md and all discovered */analysis.md files
2. **Extract Key Insights**: Identify main recommendations, concerns, and innovations from each role
3. **Identify Consensus Areas**: Find common themes across multiple roles
4. **Document Disagreements**: Capture controversial points where roles differ
@@ -371,7 +392,7 @@ Document known constraints that affect planning:
Use @ references to link back to source role analyses:
- `@role/analysis.md` - Reference entire role analysis
- `@role/analysis.md#section` - Reference specific section
- `@topic-framework.md#point-3` - Reference framework discussion point
- `@guidance-specification.md#point-3` - Reference framework discussion point
### Dynamic Role Handling