chore(skills): audit skill suite against doctor checks and forge conventions

AGENTS.md

@@ -35,8 +35,8 @@ gh pr list                          # list open pull requests
 3. **Never invent content** — use `<!-- TODO -->` markers rather than generating generic boilerplate
 4. **Conventional commits everywhere** — every skill enforces the same commit, branch, issue, and PR naming format
 5. **Standards first, compatibility second** — prefer `AGENTS.md` and Agent Skills conventions; keep vendor-specific compatibility lightweight
-6. **One invocation convention** — skills with structured primary input should support optional trailing execution context via `-- <additional context>` when additional guidance is useful
-7. **Plan before code** — for complex work, research the codebase objectively and align on architecture before writing implementation; delegate research to sub-agents for unbiased findings
+6. **One invocation convention** — every skill supports optional trailing execution context via `-- <additional context>` when additional guidance is useful
+7. **Plan before code** — for complex work, research the codebase objectively and align on architecture before writing implementation; delegate research to sub-agents for unbiased answers
 8. **Mind the instruction budget** — keep skills under ~35 instructions; delegate to sub-agents when complexity grows
 
 ## Commits

CONTEXT.md

@@ -6,47 +6,47 @@ Shared vocabulary used across multiple skills. Terms used in only one skill stay
 
 **Issue tracker** — system tracking Issues. Providers: GitHub (default, via `gh`), markdown `plan/` folder ([spec](skills/_shared/plan-folder-spec.md)), or user-configured (declared in AGENTS.md). Detection: AGENTS.md declaration → `plan/` directory → GitHub fallback.
 
-**Issue** — one tracked unit of work. Carries title, body, labels, and AFK/HITL mode.
+**Issue** — one tracked unit of work. Carries title, body, and labels; the AFK/HITL mode is recorded at creation (Issue body on GitHub, `mode` frontmatter in the markdown provider).
 
 **Plan** — structured proposal for implementing an Issue: durable decisions, vertical phases, verification steps.
 
 **Vertical slice** — end-to-end implementation crossing all layers for one narrow scenario, testable in isolation. See [vertical-slicing](skills/_shared/vertical-slicing.md).
 
+**Vertical phase** — one ordered step of a Plan: spans all affected layers, ends with tests passing and a commit. Each phase is itself slice-shaped — end-to-end, never a horizontal layer.
+
 **AFK / HITL** — Issue execution mode. AFK: fully specified for autonomous execution. HITL: requires human judgment during implementation. Set at creation time. See [afk-vs-hitl](skills/forge-create-issue/references/afk-vs-hitl.md).
 
-**Reflection** — self-review across four parallel dimensions before peer review. Produces Findings.
+**Reflection** — self-review of current changes before peer review: tiny diffs review inline, otherwise one fresh-context review pass by default, deepened only when risk justifies it. Produces Findings.
+
+**Tiny diff** — roughly ≤2 files and ≤100 changed lines with low risk; reviewed inline only when the session didn't author the changes. See [review-delegation](skills/_shared/review-delegation.md).
 
 **Finding** — one issue surfaced by reflection, severity-tagged P0–P3. P3 not flagged.
 
-**Deferred item** — a Finding not addressed in the current PR; becomes a new Issue.
+**Deferred item** — a Finding or review-feedback item not addressed in the current PR; becomes a new Issue.
 
-**Composite skill** — orchestrates other skills (currently only `forge-ship`).
+**Composite skill** — combines other skills' processes into a single invocation (currently only `forge-ship`, composing implement with the review flow shared with reflect).
 
 **Inline fallback** — `(delegate)` step provides both sub-agent and in-context paths for runtime portability.
 
-**Self-containment** — single-use references stay with the skill; cross-skill references live in `skills/_shared/`. Within the shared layer, files have explicit consumers; outside it, skills are self-contained.
+**Self-containment** — single-use references stay with the skill; cross-skill references live in `skills/_shared/`. Within the shared layer, files have explicit consumers (skills or other shared files); outside it, skills are self-contained.
 
-**Smart zone / Dumb zone** — workable region (~first 100k tokens) vs degraded region of LLM context. See [architecture — Operating Constraints](docs/architecture.md#operating-constraints).
+**Pattern audit** — when a pattern changes, grep ALL files using the old pattern and update. See [pattern-audit](skills/_shared/pattern-audit.md).
 
-**Pattern audit** — when a pattern changes, grep ALL files using the old pattern and update. See [pattern-audit](skills/forge-implement/references/pattern-audit.md).
-
-**Quality gates** — lint, format, type check, tests. Run before commit, PR push, and reflection.
+**Quality gates** — lint, format, type check, tests, and coverage (≥90% on new/modified code where tooling exists). Run at phase gates, before commit, PR push, and reflection.
 
 **Attended / unattended** — default pauses for confirmation; `--unattended` uses severity-gated heuristics.
 
 **Trailing context** — `-- <additional context>` appended to provide extra execution guidance.
 
-**Three-tier context** — Hot (`AGENTS.md`) / Warm (`docs/`) / Cold (specs). Each tier earns its token cost.
-
 ## Relationships
 
-- An **Issue** has one **AFK/HITL mode**, a priority, and labels.
-- A **Plan** implements one **Issue** through ordered **Vertical slices**.
+- An **Issue** has one **AFK/HITL mode** and labels.
+- A **Plan** implements one **Issue** through ordered **Vertical phases**.
 - A **Reflection** produces zero or more **Findings**; each is fixed or becomes a **Deferred item**.
-- A **Composite skill** invokes other skills; `--unattended` propagates through composition.
+- A **Composite skill** runs its component skills' processes; `--unattended` applies across all of them.
 
 ## Flagged Ambiguities
 
 - **Issue** (capitalized) is the abstract concept; provider determined per-project.
 - **Plan** is the proposal; "plan file" is a markdown artifact containing a Plan.
-- **Reflection** is self-review by sub-agents; **peer review** is external.
+- **Reflection** is self-review (inline for tiny diffs, otherwise delegated to fresh context); **peer review** is external.

README.md

@@ -1,6 +1,6 @@
 <p align="center">
   <strong>Agent skills for structured development with pluggable issue tracking.</strong><br>
-  One workflow. Six skills. From idea to review-ready code.
+  One workflow. Seven skills. From idea to review-ready code.
 </p>
 
 <p align="center">
@@ -32,7 +32,7 @@ Forge skills follow the [Agent Skills](https://agentskills.io) open standard and
 | Address PR Feedback | `/forge-address-pr-feedback` | Address unresolved PR review comments |
 | **Ship** | **`/forge-ship <input>`** | **Implement + review in one invocation** |
 
-Skills with structured primary input also accept optional trailing execution guidance using `-- <additional context>`.
+All skills accept optional trailing execution guidance using `-- <additional context>`.
 
 ## Workflow
 
@@ -43,7 +43,7 @@ forge-setup-project → [forge-shape →] forge-create-issue → forge-implement
                                                                         ╰──── forge-ship ────╯
 ```
 
-`forge-ship` composes implement + review into a single invocation. Review stays lean by default — tiny low-risk diffs stay inline; otherwise use one fresh-context reviewer, with a second pass only when risk justifies it. Scout and review work should use cheaper models when the runtime supports per-task model choice; otherwise they should inherit the parent session model cleanly.
+`forge-ship` composes implement + review into a single invocation; its review always delegates to a fresh-context reviewer (the session authored the diff), adding a second pass only when risk justifies it. Standalone `forge-reflect` keeps tiny diffs inline when the session didn't author them. Scout and review work should use cheaper models when the runtime supports per-task model choice; otherwise they should inherit the parent session model cleanly.
 
 ## Install