samuelnyamukapa/cmtk
An AI tester that does the grind while people keep the judgement: turn stories into test cases, run them, sort differences between an old and a new system, explore within a charter, and draft defects. Agents propose; people review and sign.
Draft defects from the latest cmtk run or compare report: one per cause, with steps to reproduce, expected and actual results, and links to the evidence, credentials removed. Files them in a tracker only after a person approves each one. Usage: /cmtk:defects [run|compare] [--file] [--manifest <file>]
Exploratory testing against a charter: probe a system within a budget, read-only, looking for bugs no story covers, and turn each finding into a draft case with its evidence. Every request is logged; the session ends with a report of what was and wasn't covered. Usage: /cmtk:explore "<charter>" [--target <name>] [--budget <requests>] [--minutes <n>] [--manifest <file>]
Turn user stories, acceptance criteria, a runbook, a requirements document or an OpenAPI file into a written test plan and draft cmtk case files, for a person to review. Every case traces to a requirement; anything unclear becomes a question, not a guess. Usage: /cmtk:plan <files or folder> [--topic <name>] [--scope "<what is in and out>"] [--manifest <file>]
Start here to test any system with the Complete Migration Toolkit: set up cmtk in the project, turn requirements into reviewed cases, run them, and get a report a person signs. Works for any project, not only migrations. Usage: /cmtk:test [<what to test>] [--url <address of the system>] [--manifest <file>]
Go through a cmtk compare report and propose, for each group of differences, whether it is noise (scrub), an intended change (drift) or a defect, with the evidence. A person accepts or rejects every proposal; nothing is written without them. Usage: /cmtk:triage [--run] [--manifest <file>]