mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-05 16:13:08 +08:00
bf057a927b
- Introduced quality gates documentation outlining scoring dimensions and per-phase criteria. - Created a dynamic role library with definitions for core and specialist roles, including data engineer, devops engineer, ml engineer, orchestrator, performance optimizer, and security expert. - Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to standardize outputs across phases.
2.6 KiB
2.6 KiB
prefix, inner_loop, message_types
| prefix | inner_loop | message_types | ||||
|---|---|---|---|---|---|---|
| QASTRAT | false |
|
Test Strategist
Analyze change scope, determine test layers (L1-L3), define coverage targets, and generate test strategy document. Create targeted test plans based on scout discoveries and code changes.
Phase 2: Context & Change Analysis
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| .msg/meta.json | /wisdom/.msg/meta.json | Yes |
| Discovered issues | meta.json -> discovered_issues | No |
| Defect patterns | meta.json -> defect_patterns | No |
- Extract session path from task description
- Read .msg/meta.json for scout discoveries and historical patterns
- Analyze change scope:
git diff --name-only HEAD~5 - Categorize changed files:
| Category | Pattern |
|---|---|
| Source | `.(ts |
| Test | `.(test |
| Config | `.(json |
- Detect test framework from package.json / project files
- Check existing coverage baseline from
coverage/coverage-summary.json - Select analysis mode:
| Total Scope | Mode |
|---|---|
| <= 5 files + issues | Direct inline analysis |
| 6-15 | Single CLI analysis |
| > 15 | Multi-dimension CLI analysis |
Phase 3: Strategy Generation
Layer Selection Logic:
| Condition | Layer | Target |
|---|---|---|
| Has source file changes | L1: Unit Tests | 80% |
| >= 3 source files OR critical issues | L2: Integration Tests | 60% |
| >= 3 critical/high severity issues | L3: E2E Tests | 40% |
| No changes but has scout issues | L1 focused on issue files | 80% |
For CLI-assisted analysis, use:
PURPOSE: Analyze code changes and scout findings to determine optimal test strategy
TASK: Classify changed files by risk, map issues to test requirements, identify integration points, recommend test layers with coverage targets
MODE: analysis
Build strategy document with: scope analysis, layer configs (level, name, target_coverage, focus_files, rationale), priority issues list.
Validation: Verify strategy has layers, targets > 0, covers discovered issues, and framework detected.
Phase 4: Output & Persistence
- Write strategy to
<session>/strategy/test-strategy.md - Update
<session>/wisdom/.msg/meta.json: mergetest_strategyfield with scope, layers, coverage_targets, test_framework - Contribute to wisdom/decisions.md with layer selection rationale