@rasensio/aidlc-content 1.26.0 → 1.26.2
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/80-review.md +7 -1
package/package.json
CHANGED
package/skills/80-review.md
CHANGED
|
@@ -24,7 +24,13 @@ You MUST perform this review with fresh eyes. If you authored the artifact being
|
|
|
24
24
|
|
|
25
25
|
## Required Artifacts
|
|
26
26
|
|
|
27
|
-
- `<artifact>.review.md` — Structured findings file in the instance namespace
|
|
27
|
+
- `<artifact>.review.md` — Structured findings file in the instance namespace, where
|
|
28
|
+
**`<artifact>` includes the artifact's own `.md`**. The findings file for
|
|
29
|
+
`requirements.md` is `requirements.md.review.md`, with the extension twice. The
|
|
30
|
+
doubled `.md` looks like a typo and is not: the gate looks artifacts up by the name
|
|
31
|
+
the template declares, so `requirements.review.md` is a file the gate cannot see.
|
|
32
|
+
`aidlc review <instance> requirements` and `aidlc review <instance> requirements.md`
|
|
33
|
+
both write the correct name, so prefer the command over hand-naming the file.
|
|
28
34
|
|
|
29
35
|
Write **one findings file per required artifact** of the phase under review. The phase's required artifacts are listed in `phase-<name>.yaml` in the instance directory — read them from there rather than from a list in this skill, because they vary per template and a project may override a template under `.aidlc/templates/`.
|
|
30
36
|
|