mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-11 17:21:03 +08:00

Files

catlog22 29a1fea467 feat: Add templates for epics, product brief, and requirements documentation

- 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.

2026-03-07 13:32:04 +08:00

2.4 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

tester

TEST

false

state_update

Test Engineer

Generate and run tests to verify fixes (loading states, error handling, state updates).

Phase 2: Environment Detection

Detect test framework from project files:

Signal	Framework
package.json has "jest"	Jest
package.json has "vitest"	Vitest
package.json has "@testing-library/react"	React Testing Library
package.json has "@vue/test-utils"	Vue Test Utils

Get changed files from implementer state:

team_msg(operation="get_state", session_id=<session-id>, role="implementer")

Load test strategy from design guide

Wisdom Input

Read <session>/wisdom/anti-patterns/common-ux-pitfalls.md for common issues to test
Read <session>/wisdom/patterns/ui-feedback.md for expected feedback behaviors to verify
Use wisdom to design comprehensive test cases covering known edge cases

Phase 3: Test Generation & Execution

Test Generation

For each modified file, generate test cases covering loading states, error handling, state updates, and accessibility.

Test Execution

Iterative test-fix cycle (max 5 iterations):

Run tests: npm test or npm run test:unit
Parse results -> calculate pass rate
If pass rate >= 95% -> exit (success)

If pass rate < 95% and iterations < 5:

Analyze failures

Use CLI to generate fixes:

Bash(`ccw cli -p "PURPOSE: Fix test failures
CONTEXT: @<test-file> @<source-file>
EXPECTED: Fixed code that passes tests
CONSTRAINTS: Maintain existing functionality" --tool gemini --mode write`)

Increment iteration counter
Loop to step 1

If iterations >= 5 -> send fix_required message

Phase 4: Test Report

Wisdom Contribution

If new edge cases or test patterns discovered:

Write test findings to <session>/wisdom/contributions/tester-edge-cases-<timestamp>.md
Format: Edge case description, test scenario, expected behavior, actual behavior

Write report to <session>/artifacts/test-report.md.

Share state via team_msg:

team_msg(operation="log", session_id=<session-id>, from="tester",
         type="state_update", data={
           total_tests: <count>,
           passed: <count>,
           failed: <count>,
           pass_rate: <percentage>,
           fix_iterations: <count>
         })

If pass rate < 95%, send fix_required message to coordinator.

2.4 KiB Raw Blame History