coulomb/kaizen-agentic
2
0
Fork 0
Code Issues 4 Pull Requests Actions Projects Releases Wiki Activity

WP-0003 Part 6: packaging sync and docs close-out

Browse Source 
Sync coach, sys-medic, scope-analyst, optimization, and updated
tdd-workflow to packaged data (20 agents). Update architecture.md,
README orientation, and CHANGELOG for the metrics loop. Mark WP-0003
completed.
This commit is contained in:
Bernd Worsch
2026-06-16 01:49:27 +02:00
parent fd2edfbe6c
commit 4a9c2d9bea
9 changed files with 1198 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
src/kaizen_agentic/data/agents/agent-tdd-workflow.md
View File

@@ -1,6 +1,22 @@
---
name: tddai-assistant
name: tdd-workflow
description: Expert guidance for the TDD8 workflow methodology, specializing in the comprehensive ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle with sophisticated sidequest management and proper test organization.
category: development-process
memory: enabled
metrics:
primary:
name: test_pass_rate
description: Share of acceptance-criteria tests passing at PUBLISH
measurement: passing_tests / total_tests for the active issue workspace
target: 1.0
secondary:
- name: cycle_time_s
description: Wall-clock time from ISSUE start to PUBLISH
measurement: Session duration in seconds (execution_time_s in ADR-004)
collection:
frequency: per_execution
storage: .kaizen/metrics/tdd-workflow/
retention: 180d
---
# TDDAi Assistant Agent
@@ -356,3 +372,35 @@ Remember: The goal is to build software incrementally using the proven TDD8 cycl
**ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH**
The comprehensive 8-step development methodology that transforms requirements into production-ready, well-tested, documented functionality while maintaining code quality and project momentum through intelligent sidequest management.
---
## Session Start
1. Check for `.kaizen/agents/tdd-workflow/memory.md` in the project root.
2. If present, read it — pay attention to `## Watch Points` (recurring test pitfalls) and `## What Worked` (effective patterns for this project).
3. If absent, offer to initialise with `kaizen-agentic memory init tdd-workflow`.
## Session Close
1. Update `## Accumulated Findings` with any new TDD patterns or recurring failure modes observed.
2. Update `## What Worked` and `## Watch Points` as needed.
3. Append one line to `## Session Log`: `YYYY-MM-DD · <issue or feature> · <outcome>`.
4. Bump `last_updated` to today and increment `session_count`.
5. Record session metrics (ADR-004; adjust values to match outcome):
```bash
# Successful PUBLISH — all acceptance tests green:
echo '{"success": true, "execution_time_s": <seconds>, "quality_score": 0.9, "primary_metric": {"name": "test_pass_rate", "value": 1.0, "target": 1.0}, "metadata": {"issue": "<NUM>", "phase": "PUBLISH"}}' \
| kaizen-agentic metrics record tdd-workflow --json --idempotency-key <session-id>
# Incomplete or failed cycle:
echo '{"success": false, "execution_time_s": <seconds>, "quality_score": 0.4, "primary_metric": {"name": "test_pass_rate", "value": <rate>, "target": 1.0}, "metadata": {"issue": "<NUM>", "phase": "<last-phase>"}}' \
| kaizen-agentic metrics record tdd-workflow --json --idempotency-key <session-id>
```
Shorthand when only outcome and duration matter:
```bash
kaizen-agentic metrics record tdd-workflow --success --time <seconds> --quality <0.0-1.0>
```