Engineer

Use a diagnosis probe to build a deterministic feedback loop that reproduces the reported failure and generates ranked falsifiable hypotheses, ensuring no code changes occur during the probing phase.

Test-driven development probing defines minimal test scenarios expected to fail against the current codebase, including explicit expected failure signatures, to establish evidence before implementation begins.

Create an implementation plan by passing a Probe Gate artifact, then generating a surgical execution handoff that carries forward acceptance criteria and probe evidence to the implementation phase.

Yes, structured JSON artifacts are required for gated, chainable execution across models or runtimes, ensuring each role consumes prior typed artifacts correctly before proceeding to the next phase.

Modifying code during the probing phase is strictly prohibited; the two-phase behavior requires separating evidence-based probing from implementation handoff to ensure safe, test-driven changes.

Yes, engineering probes support both deterministic diagnosis probes for bugs and failing test probes for features, producing evidence-based engineering plans for either work type.