forge-probe

You can test milestone viability by running disposable probes to validate hypotheses with isolated experiments. The probe framework executes rapid tests and records observable evidence, confirming whether a proposed milestone is worth pursuing before broader resource allocation.

A one-question-per-probe design isolates specific hypotheses during project planning to prevent scope creep. By restricting each disposable probe to a single viability question, the framework ensures test results remain focused and produce clear observable evidence for milestone decisions.

To run disposable probes, execute the probe workflow under the .gsd/probes directory to test milestone hypotheses. The workflow enforces the one-question-per-probe rule, generates observable evidence, and automatically updates the MANIFEST and Results sections.

Yes, running viability probes requires a minimal probe framework located under the .gsd/probes directory. This structure enforces the one-question-per-probe constraint and provides the necessary workspace for the MANIFEST and Results sections to record observable evidence.

Experimental probe findings integrate into milestone planning through the GSD workflow. The observable evidence collected from disposable probes feeds directly into plan-milestone and plan-slice phases, updating the project trajectory based on validated hypotheses.

The best way to avoid scope creep during milestone validation is enforcing a one-question-per-probe rule. This constraint ensures each disposable probe isolates a single hypothesis, producing focused observable evidence without expanding experimental boundaries.