yadflow 1.0.1 → 2.0.0

package/skills/{sdlc-status → yad-status}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: sdlc-status
-description: 'Read-only view of an SDLC epic: prints the current step, each step''s dials (assistance/automation) and status, and which approvals are still required at the active gate. For stories in the build half it also prints each back-half step''s automation dial, status, and trust record (runs / % approved-unchanged / whether it clears the threshold to be earned), plus the system-wide kill-switch state — so the team can see WHY a step is automated and reverse it with evidence. Surfaces the Phase 5 instrumentation signals: per-step "earned but manual" (nudge cost) and, across multiple epics, a fleet roll-up (scale of read). Use when the user says "sdlc status", "where is epic EP-...", "what is blocking the gate", "show the trust record", or "fleet status".'
+name: yad-status
+description: 'Read-only view of an SDLC epic: prints the current step, each step''s dials (assistance/automation) and status, and which approvals are still required at the active gate. For stories in the build half it also prints each back-half step''s automation dial, status, and trust record (runs / % approved-unchanged / whether it clears the threshold to be earned), plus the system-wide kill-switch state — so the team can see WHY a step is automated and reverse it with evidence. Surfaces the Phase 5 instrumentation signals: per-step "earned but manual" (nudge cost) and, across multiple epics, a fleet roll-up (scale of read). Use when the user says "yad status", "where is epic EP-...", "what is blocking the gate", "show the trust record", or "fleet status".'
 ---
 
 # SDLC — Status (read-only)
@@ -35,7 +35,7 @@ Print, in this order:
    `currentStep` with `→`. The full front-state chain is `[analysis → analysis-review →] epic →
    epic-review → architecture → architecture-review → ui-design → ui-design-review → stories →
    stories-review` (then `ready-for-build`); the bracketed `analysis` prefix is present only when
-   `sdlc-author-analysis` seeded it. Always render exactly the steps present in `steps[]`.
+   `yad-analysis` seeded it. Always render exactly the steps present in `steps[]`.
 3. **Active gate** — for the `currentStep` (if it is a `review+approve` step), compute and show:
    - the reviewer rule in force — **base** (`owner + 1 reviewer`), **escalated** (list the required
      domains), or **per-repo** for `stories-review` (list each repo needing sign-off),
@@ -43,7 +43,7 @@ Print, in this order:
    - approvals **still required** to pass the gate (name the missing domains/repos).
    Do not advance — just state whether the gate would pass right now.
 
-   Apply the same predicate `sdlc-review-gate` uses (restated here so this skill is
+   Apply the same predicate `yad-review-gate` uses (restated here so this skill is
    self-contained). From the `approved` records in `approvals.json` for the current step:
    - `owners` = records with `role == "owner"`; `reviewers` = distinct `role == "reviewer"`;
      `domainOwners` = `role == "domain-owner"`, grouped by `domain`.
@@ -77,7 +77,7 @@ Print, in this order:
    `⚠ earned but manual — could be machine_advance`. This is the *nudge cost* the Phase 5 trigger
    watches: automation that is proven safe but still hand-started. It is a read-only observation, not a
    recommendation to flip — earning the evidence and flipping the dial stay deliberate human acts
-   (`sdlc-run action: set-dial`). See `docs/phase-5-build-plan.md` §"What to instrument now".
+   (`yad-run action: set-dial`). See `docs/phase-5-build-plan.md` §"What to instrument now".
 
 9. **Fleet roll-up (overview only).** When the user asked for an overview, or more than one epic exists
    under `{project-root}/epics/`, print a one-line-per-epic roll-up across the fleet: each epic's
@@ -89,4 +89,4 @@ Print, in this order:
 
 ### Hard rule
 This skill is strictly read-only. If the user wants to comment, approve, or advance, point them to
-`sdlc-review-gate`.
+`yad-review-gate`.

package/skills/{sdlc-author-stories → yad-stories}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: sdlc-author-stories
+name: yad-stories
 description: 'Front state 7 of the gated SDLC. With the pm, break the approved epic into user stories, each tagged with the repos that must implement it. Assigns zero-padded EP-<slug>-S0N IDs and writes one file per story under stories/. Reads epic + architecture + contract + UI as input. Never auto-advances — hands off to the team review gate (per-repo reviewer routing). Use when the user says "author the stories" or after the UI gate passes.'
 ---
 
@@ -8,7 +8,7 @@ description: 'Front state 7 of the gated SDLC. With the pm, break the approved e
 **Goal:** Break an approved epic into human-authored, AI-assisted user stories, each with a stable
 `EP-<slug>-S0N` ID and a `repos` tag listing which repos must implement it. This is a **front state**:
 human-authored with AI assist, **never auto-advances**. When the stories are drafted, control passes
-to `sdlc-review-gate`, which routes **per-repo reviewers** (each repo's engineer reviews the stories
+to `yad-review-gate`, which routes **per-repo reviewers** (each repo's engineer reviews the stories
 touching their repo).
 
 There is **no `sm` agent** (Phase 0 Deviation 1): the `pm` lens breaks down the epic; the `pm` or
@@ -26,11 +26,11 @@ There is **no `sm` agent** (Phase 0 Deviation 1): the `pm` lens breaks down the
 ### Step 1 — Resolve the epic and check the gate
 Resolve the `EP-<slug>` (ask if not provided). Read `.sdlc/state.json`. Only proceed when
 `currentStep == "stories"` and that step's `status == "in_progress"` (the UI review must already have
-passed). If not, stop and point the user at `sdlc-status` / the gate.
+passed). If not, stop and point the user at `yad-status` / the gate.
 
 ### Step 1b — Open the authoring branch
 Open the stories authoring branch `stories/EP-<slug>` per the shared procedure
-(`../sdlc-author-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note
+(`../yad-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note
 if `{project-root}` is not a git work tree), check out the branch if it exists, else create it from the
 hub's default branch. Author and commit the story files under `stories/` on it. This is **distinct**
 from the bridge's `review/…` branch.
@@ -48,7 +48,7 @@ Phase 3 build (Spec Kit per repo) accurate anchors instead of invented ones.
 
 - **Greenfield-safe:** if `repos.json` is absent/empty, note "no repos connected" and proceed.
 - **Staleness:** if a repo's current HEAD ≠ its registry `syncedHead`, warn and suggest
-  `sdlc repo refresh <repo>` (a human decision — flag and stop, never auto-refresh); stamp
+  `yad repo refresh <repo>` (a human decision — flag and stop, never auto-refresh); stamp
   `code-context: stale` in the story frontmatter.
 - **Traceability:** record the loaded maps in each story's `code-context:` frontmatter field.
 
@@ -96,14 +96,14 @@ In `state.json`: set `stories.status: "done"`, set `stories-review.status: "in_r
 
 ### Step 7 — Stop at the gate (do NOT advance)
 Report: the story IDs created, the repos each touches, and that the next action is **review** via
-`sdlc-review-gate`. Note that this review routes **per-repo reviewers**: owner + 1 reviewer **plus**, for
+`yad-review-gate`. Note that this review routes **per-repo reviewers**: owner + 1 reviewer **plus**, for
 each repo appearing in any story's `repos`, a `domain-owner` approval for that repo. **Never record
 approval here.** Front states do not auto-advance. When the hub has a platform, the gate opens a review
-PR on the hub (via `sdlc-hub-bridge`, with a `domain:<repo>` label per touched repo) and
-`sdlc-review-gate action: sync` pulls platform approvals/comments into the ledger; otherwise the review
+PR on the hub (via `yad-hub-bridge`, with a `domain:<repo>` label per touched repo) and
+`yad-review-gate action: sync` pulls platform approvals/comments into the ledger; otherwise the review
 is recorded file-only.
 
 ## Reference
 - Story frontmatter and body template: `references/story-schema.md`.
-- State schema and field meanings: `../sdlc-author-epic/references/state-schema.md`.
-- Connecting code repos + the code-context the brain reads: `../sdlc-connect-repos/SKILL.md`.
+- State schema and field meanings: `../yad-epic/references/state-schema.md`.
+- Connecting code repos + the code-context the brain reads: `../yad-connect-repos/SKILL.md`.

package/skills/{sdlc-author-stories → yad-stories}/references/story-schema.md

@@ -40,7 +40,7 @@ As a <role>, I want <capability>, so that <outcome>.
 
 ## Per-repo review routing (the stories gate)
 
-`sdlc-review-gate` treats each repo's engineer as the `domain-owner` for the stories touching that repo.
+`yad-review-gate` treats each repo's engineer as the `domain-owner` for the stories touching that repo.
 The gate passes only when, in addition to the base rule (owner + 1 reviewer), **every repo appearing in
 any story's `repos`** has at least one `domain-owner` approval scoped to that repo (`domain` = repo
 name). The gate's `approved.md` lists which repos still lack sign-off.

package/skills/{sdlc-author-ui → yad-ui}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: sdlc-author-ui
+name: yad-ui
 description: 'Front state 5 of the gated SDLC. With the ux-designer, author ui-design.md and DESIGN.md for an approved architecture, driving Impeccable as harness slash-commands (document/extract/craft) when installed, or authoring directly when not. Reads epic + architecture as input. Never auto-advances — hands off to the team review gate. Use when the user says "author the UI design" or after the architecture gate passes.'
 ---
 
@@ -7,7 +7,7 @@ description: 'Front state 5 of the gated SDLC. With the ux-designer, author ui-d
 
 **Goal:** Produce a human-authored, AI-assisted `ui-design.md` and `DESIGN.md` for an approved
 architecture. This is a **front state**: human-authored with AI assist, **never auto-advances**. When
-the UI is drafted, control passes to `sdlc-review-gate` (base rule: owner + 1 reviewer).
+the UI is drafted, control passes to `yad-review-gate` (base rule: owner + 1 reviewer).
 
 UI work is shaped by **Impeccable**, invoked as **harness slash-commands** (not a subprocess CLI) per
 the Phase 0 deviation. If Impeccable is not installed, the `ux-designer` lens authors the same outputs
@@ -25,11 +25,11 @@ directly — the workflow does not block on the tool.
 ### Step 1 — Resolve the epic and check the gate
 Resolve the `EP-<slug>` (ask if not provided). Read `.sdlc/state.json`. Only proceed when
 `currentStep == "ui-design"` and that step's `status == "in_progress"` (the architecture review must
-already have passed). If not, stop and point the user at `sdlc-status` / the gate.
+already have passed). If not, stop and point the user at `yad-status` / the gate.
 
 ### Step 1b — Open the authoring branch
 Open the UI authoring branch `ui-design/EP-<slug>` per the shared procedure
-(`../sdlc-author-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note
+(`../yad-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note
 if `{project-root}` is not a git work tree), check out the branch if it exists, else create it from the
 hub's default branch. Author and commit `ui-design.md` / `DESIGN.md` on it. This is **distinct** from
 the bridge's `review/…` branch.
@@ -47,7 +47,7 @@ Impeccable is absent, the code-map is the brain's view of what UI/components alr
 
 - **Greenfield-safe:** if `repos.json` is absent/empty, note "no repos connected" and proceed.
 - **Staleness:** if a repo's current HEAD ≠ its registry `syncedHead`, warn and suggest
-  `sdlc repo refresh <repo>` (a human decision — flag and stop, never auto-refresh); stamp
+  `yad repo refresh <repo>` (a human decision — flag and stop, never auto-refresh); stamp
   `code-context: stale` in the frontmatter.
 - **Traceability:** record the loaded maps in the `ui-design.md` `code-context:` frontmatter field.
 
@@ -102,12 +102,12 @@ In `state.json`: set `ui-design.status: "done"`, set `ui-design-review.status: "
 
 ### Step 6 — Stop at the gate (do NOT advance)
 Report: the paths to `ui-design.md` and `DESIGN.md`, whether Impeccable was used, and that the next
-action is **review** via `sdlc-review-gate` (base rule: owner + 1 reviewer). **Never record approval
+action is **review** via `yad-review-gate` (base rule: owner + 1 reviewer). **Never record approval
 here.** Front states do not auto-advance. When the hub has a platform, the gate opens a review PR on the
-hub (via `sdlc-hub-bridge`) and `sdlc-review-gate action: sync` pulls platform approvals/comments into
+hub (via `yad-hub-bridge`) and `yad-review-gate action: sync` pulls platform approvals/comments into
 the ledger; otherwise the review is recorded file-only.
 
 ## Reference
 - Impeccable commands and the slash-command-vs-CLI deviation: `RESEARCH-NOTES.md` §4 + Deviation 3.
-- State schema and field meanings: `../sdlc-author-epic/references/state-schema.md`.
-- Connecting code repos + the code-context the brain reads: `../sdlc-connect-repos/SKILL.md`.
+- State schema and field meanings: `../yad-epic/references/state-schema.md`.
+- Connecting code repos + the code-context the brain reads: `../yad-connect-repos/SKILL.md`.