@fro.bot/systematic 3.13.3 → 3.13.4
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 +1 -1
- package/skills/ce-plan/SKILL.md +2 -0
package/package.json
CHANGED
package/skills/ce-plan/SKILL.md
CHANGED
|
@@ -443,6 +443,8 @@ For each unit, include:
|
|
|
443
443
|
|
|
444
444
|
Every feature-bearing unit should include the test file path in `**Files:**`.
|
|
445
445
|
|
|
446
|
+
When a unit creates a file in a directory that carries registration obligations — a manifest, index, codemap, module table, or generated artifact that must list it — name those surfaces in the same unit's `**Files:**`, and name the regeneration command in its `**Verification**`. Phase 1.1 already collects this from the repository's own contributor guidance; carry it into the unit rather than leaving it for a failing gate to report. An obligation that no gate enforces is the one most likely to be missed, so state it even when nothing will fail.
|
|
447
|
+
|
|
446
448
|
Use `Execution note` sparingly. Good uses include:
|
|
447
449
|
- `Execution note: Start with a failing integration test for the request/response contract.`
|
|
448
450
|
- `Execution note: Add characterization coverage before modifying this legacy parser.`
|