speccrew 0.6.62 → 0.6.63
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.
|
@@ -164,9 +164,7 @@ For each platform, generates:
|
|
|
164
164
|
- Multiple modules MUST NOT share the same entryDirs value. If multiple business areas share the same directory, they belong to ONE module.
|
|
165
165
|
- If the generated JSON does not match this format, you MUST regenerate it before proceeding
|
|
166
166
|
</field>
|
|
167
|
-
<field name="text">
|
|
168
|
-
<field name="text">DO NOT generate any additional files such as reports (.md), logs, or summaries.</field>
|
|
169
|
-
<field name="text">Any extra files beyond the entry-dirs JSON are considered errors.</field>
|
|
167
|
+
<field name="text">Output is strictly the entry-dirs JSON file at the specified output path. Per xml-workflow-spec.md "Strict Block Adherence" rule, no extra files are permitted.</field>
|
|
170
168
|
</block>
|
|
171
169
|
|
|
172
170
|
<!-- Checkpoint: Persist Generated JSON -->
|
package/package.json
CHANGED
|
@@ -482,6 +482,19 @@ Team Leader executes:
|
|
|
482
482
|
7. **`rule level="forbidden"`** = immediate stop if violated
|
|
483
483
|
8. **Input/Output blocks** define the contract — respect required parameters
|
|
484
484
|
|
|
485
|
+
### Strict Block Adherence
|
|
486
|
+
|
|
487
|
+
When executing an XML workflow, the Agent MUST strictly follow the block sequence defined in the workflow:
|
|
488
|
+
|
|
489
|
+
1. **Only perform actions defined by blocks** — Every action the Agent takes must correspond to a specific block in the workflow. The Agent MUST NOT perform any actions not defined by the blocks.
|
|
490
|
+
2. **Prohibited extra actions** include but are not limited to:
|
|
491
|
+
- Generating files not specified in block output paths (e.g. summary reports, analysis documents, logs)
|
|
492
|
+
- Running scripts or commands not defined in any block
|
|
493
|
+
- Creating intermediate/temporary files outside of block definitions
|
|
494
|
+
- Adding "bonus" analysis steps or documentation beyond what blocks require
|
|
495
|
+
3. **Output scope** — The workflow's output is strictly limited to what is defined in `output` blocks or block-level output fields (`<field name="output">`). Any file or artifact not traceable to a block definition is considered an error.
|
|
496
|
+
4. **When in doubt, don't do it** — If an action is not explicitly defined in any block, the Agent must skip it, even if it seems "helpful".
|
|
497
|
+
|
|
485
498
|
### Block Execution Announcement Protocol
|
|
486
499
|
|
|
487
500
|
Before executing each `<block>`, the agent MUST announce the block being executed. The announcement format is:
|