trace

Manual trace-through verification catches logic errors that automated testing misses by applying deterministic scenarios across code, workflows, and documents. It uses domain adapters to trace happy path, error path, and edge case execution states.

Manual trace-through verification is a state-table driven technique to detect logic gaps and edge cases in code and workflows. It validates deterministic scenarios including happy path, error path, and edge case execution paths.

Yes, manual trace verification generates Markdown-based TRACE reports with line-numbered findings and Mermaid visualizations. These context-rich artifacts support RCA integration and cross-team collaboration audits.

Yes, domain adapters enable state-table driven tracing across code, skills, workflows, and documents. They apply deterministic scenarios to verify logic and detect integration issues across multiple domains.

Run the /trace command on your target to start manual verification. The process applies domain adapters and generates TRACE reports with Mermaid visualizations and line-numbered findings for cross-team collaboration.

Use manual trace when automated testing misses logic gaps, edge cases, or integration issues across workflows and documents. It provides deterministic state-table tracing and RCA-ready artifacts where automated coverage falls short.