@eltonssouza/development-utility-kit 0.15.0 → 0.16.0

package/.claude/skills/triage/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: triage
+description: Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
+---
+
+# Triage
+
+Move issues on the project issue tracker through a small state machine of triage roles.
+
+Every comment or issue posted to the issue tracker during triage **must** start with this disclaimer:
+
+```
+> *This was generated by AI during triage.*
+```
+
+## Reference docs
+
+- [AGENT-BRIEF.md](AGENT-BRIEF.md) — how to write durable agent briefs
+- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md) — how the `.out-of-scope/` knowledge base works
+
+## Roles
+
+Two **category** roles:
+
+- `bug` — something is broken
+- `enhancement` — new feature or improvement
+
+Five **state** roles:
+
+- `needs-triage` — maintainer needs to evaluate
+- `needs-info` — waiting on reporter for more information
+- `ready-for-agent` — fully specified, ready for an AFK agent
+- `ready-for-human` — needs human implementation
+- `wontfix` — will not be actioned
+
+Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
+
+These are canonical role names — the actual label strings used in the issue tracker may differ. The mapping should have been provided to you - run `/setup-matt-pocock-skills` if not.
+
+State transitions: an unlabeled issue normally goes to `needs-triage` first; from there it moves to `needs-info`, `ready-for-agent`, `ready-for-human`, or `wontfix`. `needs-info` returns to `needs-triage` once the reporter replies. The maintainer can override at any time — flag transitions that look unusual and ask before proceeding.
+
+## Invocation
+
+The maintainer invokes `/triage` and describes what they want in natural language. Interpret the request and act. Examples:
+
+- "Show me anything that needs my attention"
+- "Let's look at #42"
+- "Move #42 to ready-for-agent"
+- "What's ready for agents to pick up?"
+
+## Show what needs attention
+
+Query the issue tracker and present three buckets, oldest first:
+
+1. **Unlabeled** — never triaged.
+2. **`needs-triage`** — evaluation in progress.
+3. **`needs-info` with reporter activity since the last triage notes** — needs re-evaluation.
+
+Show counts and a one-line summary per issue. Let the maintainer pick.
+
+## Triage a specific issue
+
+1. **Gather context.** Read the full issue (body, comments, labels, reporter, dates). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read `.out-of-scope/*.md` and surface any prior rejection that resembles this issue.
+
+2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.
+
+3. **Reproduce (bugs only).** Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong `needs-info` signal). A confirmed repro makes a much stronger agent brief.
+
+4. **Grill (if needed).** If the issue needs fleshing out, run a `/grill-with-docs` session.
+
+5. **Apply the outcome:**
+   - `ready-for-agent` — post an agent brief comment ([AGENT-BRIEF.md](AGENT-BRIEF.md)).
+   - `ready-for-human` — same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
+   - `needs-info` — post triage notes (template below).
+   - `wontfix` (bug) — polite explanation, then close.
+   - `wontfix` (enhancement) — write to `.out-of-scope/`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).
+   - `needs-triage` — apply the role. Optional comment if there's partial progress.
+
+## Quick state override
+
+If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to `ready-for-agent` without a grilling session, ask whether they want to write an agent brief.
+
+## Needs-info template
+
+```markdown
+## Triage Notes
+
+**What we've established so far:**
+
+- point 1
+- point 2
+
+**What we still need from you (@reporter):**
+
+- question 1
+- question 2
+```
+
+Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".
+
+## Resuming a previous session
+
+If prior triage notes exist on the issue, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.

package/.claude/skills/zoom-out/SKILL.md

@@ -0,0 +1,7 @@
+---
+name: zoom-out
+description: Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
+disable-model-invocation: true
+---
+
+I don't know this area of code well. Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary vocabulary.

package/README.md

@@ -28,10 +28,10 @@ npx @eltonssouza/development-utility-kit install
 
 Stands on the best community skills & plugins — recommended, not bundled (the installer prints this too):
 
-- **Impeccable** (frontend design gate) — `npx impeccable skills install`
+- **Impeccable** (frontend design gate) — `/plugin marketplace add pbakaus/impeccable` then `/plugin install impeccable` *(cross-platform; npx route needs `unzip` on Windows)*
 - **Caveman** (token-saving output) — `npm install -g @juliusbrussee/caveman-code`
-- **RTK** (token-killer CLI proxy) — `brew install rtk` *(macOS)*
-- **Grill-me** (discovery interview) — `npx skills@latest add mattpocock/skills`
+- **RTK** (token-killer CLI proxy) — `cargo install rtk` *(or `brew install rtk` on macOS)*
+- **Grill-me** (discovery interview) — `npx skills@latest add mattpocock/skills` *(needs `unzip` on Windows)*
 
 ## What you get
 

package/README.npm.md

@@ -28,10 +28,10 @@ npx @eltonssouza/development-utility-kit install
 
 Stands on the best community skills & plugins — recommended, not bundled (the installer prints this too):
 
-- **Impeccable** (frontend design gate) — `npx impeccable skills install`
+- **Impeccable** (frontend design gate) — `/plugin marketplace add pbakaus/impeccable` then `/plugin install impeccable` *(cross-platform; npx route needs `unzip` on Windows)*
 - **Caveman** (token-saving output) — `npm install -g @juliusbrussee/caveman-code`
-- **RTK** (token-killer CLI proxy) — `brew install rtk` *(macOS)*
-- **Grill-me** (discovery interview) — `npx skills@latest add mattpocock/skills`
+- **RTK** (token-killer CLI proxy) — `cargo install rtk` *(or `brew install rtk` on macOS)*
+- **Grill-me** (discovery interview) — `npx skills@latest add mattpocock/skills` *(needs `unzip` on Windows)*
 
 ## What you get
 

package/README.repo.md

@@ -33,10 +33,10 @@ development-utility-kit stands on the best community skills & plugins. They are
 
 | Companion | What it adds | Install |
 |---|---|---|
-| **Impeccable** | frontend design gate (polish / audit / critique) — wired into `project-manager` §6.6 | `npx impeccable skills install` |
+| **Impeccable** | frontend design gate (polish / audit / critique) — wired into `project-manager` §6.6 | `/plugin marketplace add pbakaus/impeccable` then `/plugin install impeccable` *(git-based, cross-platform; the `npx impeccable skills install` route needs `unzip` and breaks on Windows)* |
 | **Caveman** | token-saving telegraphic output (~75% fewer tokens) | `npm install -g @juliusbrussee/caveman-code` |
-| **RTK** | Rust Token Killer CLI proxy (60–90% savings) — powers the dashboard widget | `brew install rtk` *(macOS; see RTK repo for Windows/Linux)* |
-| **Grill-me** | relentless discovery interview (opens the delivery pipeline) | `npx skills@latest add mattpocock/skills` |
+| **RTK** | Rust Token Killer CLI proxy (60–90% savings) — powers the dashboard widget | `cargo install rtk` *(cross-platform; or `brew install rtk` on macOS)* |
+| **Grill-me** | relentless discovery interview (opens the delivery pipeline) | `npx skills@latest add mattpocock/skills` *(needs `unzip` on PATH on Windows)* |
 
 ---
 
@@ -404,7 +404,7 @@ Full vault under [`docs/brain/`](docs/brain/) — browse via Obsidian. Live ADR
 
 Honest thanks to:
 
-- **[`grill-me`](https://github.com/mattpocock/skills)** — by **[Matt Pocock](https://github.com/mattpocock)** ([aihero.dev](https://www.aihero.dev/my-grill-me-skill-has-gone-viral)). The relentless discovery interview that opens our `grill-me → to-prd → to-issues → analyst → run-sprint` pipeline is Matt's design. We adapted the skill to persist its output to `docs/discovery/DISCOVERY_*.md` and hand off to `analyst`, but the interview mechanic — one decision branch at a time, with a recommended answer the user just confirms — is his.
+- **[`mattpocock/skills`](https://github.com/mattpocock/skills)** — by **[Matt Pocock](https://github.com/mattpocock)** ([aihero.dev](https://www.aihero.dev/my-grill-me-skill-has-gone-viral)). The relentless `grill-me` discovery interview is Matt's design. As of **v0.16.0** the harness is **adopting Matt's full issue-tracker engineering workflow** (ADR-049, MIT): we **vendor** his skills — `diagnose`, `grill-with-docs`, `improve-codebase-architecture`, `prototype`, `setup-matt-pocock-skills`, `tdd`, `triage`, `zoom-out` (and, in a later sprint, `to-prd`/`to-issues`) — under `.claude/skills/` with his `LICENSE` + a `NOTICE` (see `.claude/skills/_vendor/`). They are bundled, not re-authored; upstream is the source of truth. The staged migration is in `docs/plans/PLAN_mattpocock-workflow-adoption.md`.
 - **[`caveman`](https://github.com/JuliusBrussee/caveman)** — by **[Julius Brussee](https://github.com/JuliusBrussee)**. The telegraphic communication mode that saves us 65–75% of output tokens with zero technical loss. We use it as the default style in this harness; the compression rules, the levels (lite/full/ultra), and the auto-clarity carve-outs are Julius's work.
 - **[`impeccable`](https://github.com/pbakaus/impeccable)** — by **[Paul Bakaus](https://github.com/pbakaus)**. The design-refinement skill (`polish | harden | audit`) that drives our visual-quality gate. Paul's `npx skills add pbakaus/impeccable` distribution pattern also directly inspired our own `npx @eltonssouza/development-utility-kit install` installer (ADR-018).
 - **[`rtk`](https://github.com/rtk-ai/rtk)** — by the **[rtk-ai](https://github.com/rtk-ai) team**. The Rust Token Killer CLI proxy that powers the live "RTK savings" widget on the `duk dashboard` (`rtk gain --format json` → `/api/rtk`). The 60–90% savings on dev operations we surface in the dashboard are RTK's, not ours.

package/bin/cli.js

@@ -491,10 +491,10 @@ function adoptProject(opts) {
  * each is installed separately by the user (per ADR-010 / Acknowledgements).
  */
 const COMPANIONS = [
-  { name: 'Impeccable', what: 'frontend design gate (polish / audit / critique)', cmd: 'npx impeccable skills install' },
+  { name: 'Impeccable', what: 'frontend design gate (polish / audit / critique)', cmd: '/plugin marketplace add pbakaus/impeccable', note: 'in Claude Code, then /plugin install impeccable — git-based, cross-platform' },
   { name: 'Caveman', what: 'token-saving telegraphic output (~75% fewer tokens)', cmd: 'npm install -g @juliusbrussee/caveman-code' },
-  { name: 'RTK', what: 'Rust Token Killer CLI proxy (60-90% savings)', cmd: 'brew install rtk', note: 'macOS; see the RTK repo for Windows/Linux' },
-  { name: 'Grill-me', what: 'relentless discovery interview', cmd: 'npx skills@latest add mattpocock/skills' },
+  { name: 'RTK', what: 'Rust Token Killer CLI proxy (60-90% savings)', cmd: 'cargo install rtk', note: 'cross-platform; or brew install rtk on macOS' },
+  { name: 'Grill-me', what: 'relentless discovery interview', cmd: 'npx skills@latest add mattpocock/skills', note: 'needs unzip on PATH on Windows' },
 ];
 
 /**

package/bin/lib/lint.js

@@ -174,9 +174,23 @@ function findStackPacks() {
 // ── Category 1: skills.frontmatter ──────────────────────────────────────────
 
 const SKILL_REQUIRED_FIELDS = ['name', 'description', 'tools', 'model'];
+// Vendored third-party skills are valid Claude Code skills as-authored upstream;
+// `tools`/`model` are a harness-internal convention, not a Claude Code requirement.
+const VENDORED_REQUIRED_FIELDS = ['name', 'description'];
+
+function loadVendoredSkillNames() {
+  try {
+    const p = path.join(packageRoot(), '.claude', 'skills', '_vendor', 'vendored.json');
+    const data = JSON.parse(fs.readFileSync(p, 'utf8'));
+    return new Set(Array.isArray(data.skills) ? data.skills : []);
+  } catch {
+    return new Set();
+  }
+}
 
 function checkSkillsFrontmatter() {
   const violations = [];
+  const vendored = loadVendoredSkillNames();
   for (const skill of findSkills()) {
     const content = readSafe(skill.path);
     if (content === null) {
@@ -184,7 +198,8 @@ function checkSkillsFrontmatter() {
       continue;
     }
     const { frontmatter } = extractFrontmatter(content);
-    for (const f of SKILL_REQUIRED_FIELDS) {
+    const required = vendored.has(skill.name) ? VENDORED_REQUIRED_FIELDS : SKILL_REQUIRED_FIELDS;
+    for (const f of required) {
       if (!frontmatter[f]) {
         violations.push({
           category: 'skills', severity: ERROR, file: skill.path, line: 1,

package/dashboard/public/content/docs/skills-reference.en.md

@@ -47,7 +47,7 @@ This document covers the 18 official skills of the harness, grouped by purpose.
 
 Reference: **ADR-033** — orchestrate mode fills the fast-lane gap acknowledged in ADR-008 §Consequences ("8 etapas para feature pequena é cerimônia").
 
-**Frontend design gate (§6.6, ADR-048)**: whenever the dispatch touches the `frontend`/`ux` domain, `project-manager` **must offer the external `impeccable` design gate** (mandatory offer; the user chooses). On "Sim" it runs, in order: install if absent (`npx skills add pbakaus/impeccable`, terminal, per-project) → `/impeccable teach` (analyze project) → `/impeccable <verb>` (polish/audit/…) → then resumes orchestration. Impeccable is a tool, not the authority; `project-manager` never auto-runs it and never abdicates control. Extends ADR-010's gate-keeper WARN check.
+**Frontend design gate (§6.6, ADR-048)**: whenever the dispatch touches the `frontend`/`ux` domain, `project-manager` **must offer the external `impeccable` design gate** (mandatory offer; the user chooses). On "Sim" it runs, in order: install if absent (prefer `/plugin marketplace add pbakaus/impeccable` + `/plugin install impeccable` — git-based, cross-platform; the `npx` route needs `unzip` and breaks on Windows) → `/impeccable teach` (analyze project) → `/impeccable <verb>` (polish/audit/…) → then resumes orchestration. Impeccable is a tool, not the authority; `project-manager` never auto-runs it and never abdicates control. Extends ADR-010's gate-keeper WARN check.
 
 **Delegated agent(s)**: variable, per internal routing table. ROUTE dispatches 1; ORCHESTRATE dispatches 2–5 in parallel.
 

package/dashboard/public/content/manual/frontend.en.md

@@ -322,9 +322,10 @@ The harness exposes skills that trigger by **keyword** in Claude Code/Cowork con
 ```
 front detectada → PM pergunta "usar impeccable?"
   └─ Sim:
-       1. [terminal, no projeto]  npx skills add pbakaus/impeccable   (só se ausente)
-       2. [claude code]           /impeccable teach                   (analisa o projeto)
-       3. [claude code]           /impeccable <verbo>                 (polish / audit / …)
+       1. [claude code]  /plugin marketplace add pbakaus/impeccable  (só se ausente)
+                         /plugin install impeccable
+       2. [claude code]  /impeccable teach                           (analisa o projeto)
+       3. [claude code]  /impeccable <verbo>                         (polish / audit / …)
        → project-manager retoma a orquestração
 ```
 
@@ -335,13 +336,14 @@ The offer is mandatory, the use is yours — same gating philosophy as `grill-me
 - Author: Paul Bakaus
 - Repo: `github.com/pbakaus/impeccable`
 
-### Installation (gate 1 — terminal, per-project)
+### Installation (gate 1 — Claude Code, cross-platform)
 
-```bash
-npx skills add pbakaus/impeccable
+```
+/plugin marketplace add pbakaus/impeccable
+/plugin install impeccable
 ```
 
-Installs into the **selected project's** `.claude/skills/` — the `/impeccable *` commands then become available in that project's Claude Code chat. `project-manager` runs this automatically when you accept the offer and impeccable is not yet present.
+Git-based — no `unzip` needed, so it works on Windows. The `/impeccable *` commands then become available in chat. (The `npx skills add pbakaus/impeccable` / `npx impeccable skills install` routes depend on `unzip` and fail on stock Windows.) `project-manager` runs this automatically when you accept the offer and impeccable is not yet present.
 
 ### Available commands (gates 2 & 3 — Claude Code)
 

package/dashboard/public/content/manual/fullstack.en.md

@@ -353,11 +353,14 @@ fullstack project.
 > installs if absent, runs `/impeccable teach` (analyzes the project), then the
 > action verb — and resumes control. See the [frontend manual](frontend) §5.
 
-**Install** (gate 1 — once per project, terminal):
+**Install** (gate 1 — in Claude Code, cross-platform):
 
-```bash
-npx skills add pbakaus/impeccable
 ```
+/plugin marketplace add pbakaus/impeccable
+/plugin install impeccable
+```
+
+Git-based, no `unzip` — works on Windows. (The `npx` install routes need `unzip` and fail on stock Windows.)
 
 **Available commands**:
 
@@ -1424,9 +1427,9 @@ Details: [hooks-reference](../docs/hooks-reference).
 - **Senior+ gate**: set of thresholds (coverage, mutation, a11y,
   Lighthouse, pyramid ratio) that blocks merge.
 - **Vault**: `docs/brain/` in Obsidian format (wiki links + tags + MOC).
-- **Impeccable**: external pack (`npx skills add pbakaus/impeccable`) with
-  `/impeccable polish|audit|harden|typeset|colorize|layout` commands for
-  visual polish.
+- **Impeccable**: external plugin (`/plugin marketplace add pbakaus/impeccable`
+  then `/plugin install impeccable`) with `/impeccable teach|shape|polish|audit|
+  critique|harden` commands for visual polish.
 - **openapi-typescript**: TS type generator from OpenAPI 3.x.
 - **Goal-ready**: explicit, measurable, tied to the objective.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eltonssouza/development-utility-kit",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "npx installer for the development-utility-kit harness",
   "bin": {
     "duk": "bin/cli.js"