@emiliosp/pi-maestro 0.5.0 → 0.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -44,6 +44,15 @@ Every probe remains mandatory for builder and verifier.
|
|
|
44
44
|
The builder chooses test code, fixtures, mocks, and commands.
|
|
45
45
|
Do not copy agent procedures, repository rules, investigation logs, or workflow history into the spec.
|
|
46
46
|
|
|
47
|
+
During spec preparation and revisions, identify the decisions and unresolved facts that each open question depends on.
|
|
48
|
+
Ask a question only after its prerequisite decisions are settled and the relevant investigation is complete.
|
|
49
|
+
After each owner answer or investigation result, update the remaining questions and remove those that no longer apply.
|
|
50
|
+
If an earlier decision changes, review the decisions that depend on it.
|
|
51
|
+
|
|
52
|
+
Before requesting approval for an initial or revised spec, check that all decisions needed for the agreed scope are explicit.
|
|
53
|
+
Resolve open decisions with the owner before requesting approval. Do not leave necessary decisions as implicit assumptions.
|
|
54
|
+
Do not extend this check to routine implementation choices that belong to the builder.
|
|
55
|
+
|
|
47
56
|
During spec preparation and revisions, investigate each technical decision before presenting options or recommending an answer. Do not wait for the owner to request code analysis.
|
|
48
57
|
Trace the relevant code and data flow across affected components, including transformations that limit the available data.
|
|
49
58
|
Use repository evidence to explain each option's feasibility, required changes, scope, and effects on existing behavior.
|