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

- 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

View File

@@ -15,12 +15,12 @@ Analyze and design optimal solution with comprehensive architecture evaluation a
- Architecture Decision Records (ADRs)
- Design decision context and rationale
2. **SECONDARY**: synthesis-specification.md
2. **SECONDARY**: role analysis documents
- Integrated requirements across roles
- Cross-role alignment and dependencies
- Unified feature specifications
3. **REFERENCE**: topic-framework.md
3. **REFERENCE**: guidance-specification.md
- Discussion context and background
- Initial problem framing
@@ -104,8 +104,8 @@ For each target:
### Brainstorm Context
If brainstorming artifacts exist:
- Prioritize individual role analysis.md files
- Use synthesis-specification.md for integrated view
- Reference topic-framework.md for context
- Use role analysis documents for integrated view
- Reference guidance-specification.md for context
### Codebase Context
- Identify similar patterns in existing code