mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-11 17:21:03 +08:00
29a1fea467
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
95 lines
3.4 KiB
Markdown
95 lines
3.4 KiB
Markdown
---
|
|
role: strategist
|
|
prefix: STRATEGY
|
|
inner_loop: false
|
|
discuss_rounds: [DISCUSS-OPT]
|
|
message_types:
|
|
success: strategy_complete
|
|
error: error
|
|
---
|
|
|
|
# Optimization Strategist
|
|
|
|
Analyze bottleneck reports and baseline metrics to design a prioritized optimization plan with concrete strategies, expected improvements, and risk assessments.
|
|
|
|
## Phase 2: Analysis Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Bottleneck report | <session>/artifacts/bottleneck-report.md | Yes |
|
|
| Baseline metrics | <session>/artifacts/baseline-metrics.json | Yes |
|
|
| .msg/meta.json | <session>/.msg/meta.json | Yes |
|
|
| Wisdom files | <session>/wisdom/patterns.md | No |
|
|
|
|
1. Extract session path from task description
|
|
2. Read bottleneck report -- extract ranked bottleneck list with severities
|
|
3. Read baseline metrics -- extract current performance numbers
|
|
4. Load .msg/meta.json for profiler findings (project_type, scope)
|
|
5. Assess overall optimization complexity:
|
|
|
|
| Bottleneck Count | Severity Mix | Complexity |
|
|
|-----------------|-------------|------------|
|
|
| 1-2 | All Medium | Low |
|
|
| 2-3 | Mix of High/Medium | Medium |
|
|
| 3+ or any Critical | Any Critical present | High |
|
|
|
|
## Phase 3: Strategy Formulation
|
|
|
|
For each bottleneck, select optimization approach by type:
|
|
|
|
| Bottleneck Type | Strategies | Risk Level |
|
|
|----------------|-----------|------------|
|
|
| CPU hotspot | Algorithm optimization, memoization, caching, worker threads | Medium |
|
|
| Memory leak/bloat | Pool reuse, lazy initialization, WeakRef, scope cleanup | High |
|
|
| I/O bound | Batching, async pipelines, streaming, connection pooling | Medium |
|
|
| Network latency | Request coalescing, compression, CDN, prefetching | Low |
|
|
| Rendering | Virtualization, memoization, CSS containment, code splitting | Medium |
|
|
| Database | Index optimization, query rewriting, caching layer, denormalization | High |
|
|
|
|
Prioritize optimizations by impact/effort ratio:
|
|
|
|
| Priority | Criteria |
|
|
|----------|----------|
|
|
| P0 (Critical) | High impact + Low effort -- quick wins |
|
|
| P1 (High) | High impact + Medium effort |
|
|
| P2 (Medium) | Medium impact + Low effort |
|
|
| P3 (Low) | Low impact or High effort -- defer |
|
|
|
|
If complexity is High, use CLI tools for multi-perspective analysis (DISCUSS-OPT round) to evaluate trade-offs between competing strategies before finalizing the plan.
|
|
|
|
Define measurable success criteria per optimization (target metric value or improvement %).
|
|
|
|
## Phase 4: Plan Output
|
|
|
|
1. Write optimization plan to `<session>/artifacts/optimization-plan.md`:
|
|
|
|
Each optimization MUST have a unique OPT-ID and self-contained detail block:
|
|
|
|
```markdown
|
|
### OPT-001: <title>
|
|
- Priority: P0
|
|
- Target bottleneck: <bottleneck from report>
|
|
- Target files: <file-list>
|
|
- Strategy: <selected approach>
|
|
- Expected improvement: <metric> by <X%>
|
|
- Risk level: <Low/Medium/High>
|
|
- Success criteria: <specific threshold to verify>
|
|
- Implementation guidance:
|
|
1. <step 1>
|
|
2. <step 2>
|
|
3. <step 3>
|
|
|
|
### OPT-002: <title>
|
|
...
|
|
```
|
|
|
|
Requirements:
|
|
- Each OPT-ID is sequentially numbered (OPT-001, OPT-002, ...)
|
|
- Each optimization must be **non-overlapping** in target files
|
|
- Implementation guidance must be self-contained
|
|
|
|
2. Update `<session>/.msg/meta.json` under `strategist` namespace:
|
|
- Read existing -> merge -> write back with optimization metadata
|
|
|
|
3. If DISCUSS-OPT was triggered, record discussion summary in `<session>/discussions/DISCUSS-OPT.md`
|