@antoneeo/agentic-sdlc-skill 1.43.1 → 1.48.0

package/skills/agentic-sdlc-skill/templates.md

@@ -393,6 +393,14 @@ checks: [marketing.funnel]      # optional — extra portable checks to run on t
 | persist an order | EXISTS | `path/to/store.py#OrderStore` | re-read `save()`: durable, returns the id |
 | notify the customer | MISSING | — | grep notify/alert/dispatch + send, over src/ and legacy/; no owner |
 
+## Guide check
+<!-- the Phase-3 question (SKILL.md "Would a guide be worth writing here?"),
+     answered while the model is being paid for. Two lines, both always filled:
+     a "yes" on the second makes writing the `source_kind: code` guide a duty
+     (`guides.md` §1). `validate` notes an L3 that leaves this unanswered. -->
+- CURRENT guide covering what this touches: `GUIDE_x.md` / none
+- High-complexity component understood here that no guide covers: no / yes — `component` (guide written: `GUIDE_y.md`)
+
 ## Impact
 <!-- existing files touched, APIs/contracts, performance, new dependencies.
      Derived from the ledger above: every INADEQUATE/MISSING row appears here. -->
@@ -416,7 +424,8 @@ checks: [marketing.funnel]      # optional — extra portable checks to run on t
      dated the day it was written. An undated paragraph is read as part of the
      dated entry above it, so a new event never starts undated; `####`
      sub-headings inside an entry are fine. It is the handoff source for this
-     feature. -->
+     feature.
+     A deferred fix of code contradicting a `topics/` claim cites the claim id here (SKILL.md Write Triggers). -->
 ```
 
 Allowed frontmatter states: `PLANNED` | `IN_PROGRESS` | `COMPLETED` | `CANCELLED`. `COMPLETED` requires `end_date`. (The validator also accepts the deprecated Italian keys `stato`/`livello`/`data_inizio`/`data_fine` in existing projects.)
@@ -698,7 +707,8 @@ columns: Standalone adds `reviewer`, a Hybrid row adds `instrument` and
 and `closure` (Standalone); `deep`, `light`, `code`, `guide`, `vision` (devPNT gates
 and the Vision blind check). `model` is a different question about the same review: `tier` says WHICH GATE ran,
 `model` says WHAT CAPABILITY ran it (`deep`, `light`, `economy`,
-`single (client exposes no choice)`, `below floor: <reason>` — the floor and its
+`single (client exposes no choice)`, `below floor: <reason>`, `none (not due)` on a
+NOT DUE row — the floor and its
 arbitration are `review.md` §The capability floor). The two columns share the words
 `deep`/`light` and mean different things by them, which is why they are read by
 header and never by position. The validator reads this column by its header name, so
@@ -723,6 +733,7 @@ round verifies them (`review.md` §Receiving) — and 3 is the ceiling, past whi
 residue goes to the user rather than into a fourth round. `verdict` carries the
 round-1 verdict and the final one when they differ (`FAIL → PASS`): collapsing a
 first-round FAIL into a bare `PASS` erases the evidence this log exists to keep.
+A restating delta ruled not due (`review.md` §When a review is due) is still a row: `tier` `closure`, `model` `none (not due)`, findings and rounds `0`, verdict `NOT DUE: <the kinds; the check that ran and its result>`; `benefit` counts it apart.
 Concurrent reviews: `init` writes a `.gitattributes` stanza giving this file
 `merge=union` — a **built-in** driver (no per-clone `git config`, unlike
 `merge=ours`, which silently does nothing until every clone configures it).