infinity-harness 2.0.0 → 2.0.1

package/CHANGELOG.md

@@ -4,6 +4,65 @@ All notable changes to this project are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.1] — 2026-08-23
+
+### Fixed
+
+- **pi printed a skill conflict on every start.** `harness/skills/README.md` was a README, and pi
+  loads *every* `.md` in a declared skills directory as a skill — so every session opened with
+  `[Skill conflicts] … description is required`. The README moved to `harness/docs/skills.md`, and
+  `tests/skills.test.ts` now audits the shipped skills against pi's own rules (frontmatter present,
+  `description` non-empty and within length, `name` lowercase-and-hyphens, matching its filename, no
+  duplicates, no UTF-8 BOM hiding the header). A warning the user saw at runtime is a failure we see
+  at test time.
+- **Four shipped skills told the agent to run a CLI that does not exist.**
+  `capability-acquisition`, `building-tools`, `writing-skills` and the deleted MCP skill all
+  instructed the model to register capabilities with `infinity-harness capability add …` — a command
+  from the `dev-harness` ancestor that this package never had. An agent following them got stuck at
+  3am on a command not found. Rewritten around what pi actually provides: a skill file in
+  `.pi/skills/`, a script in the repo, or an extension via `pi install`.
+
+### Removed
+
+- **`building-mcp-servers.md`**, and every other reference to MCP. pi has no MCP client — no
+  dependency, no configuration, no code — so a skill about scaffolding MCP servers and registering
+  them could only send the agent somewhere pi cannot follow. This is a pi extension; MCP was
+  another system's answer.
+- **`harness/capability/sources.json` and `harness/tools/`.** Neither was read by any code, neither
+  was published, and both documented the same missing CLI.
+
+### Added
+
+- **The brief names the skills that match the work.** The docs claimed it did; nothing implemented
+  it. Every skill now declares a `kind` — `process` (belongs to its phase), `domain` (needs to share
+  vocabulary with the task) or `meta` (asked for explicitly) — and the brief ranks them by phase
+  position, tag hits and name mentions, showing the best two. A task about *"two workers racing on
+  the lock"* gets `concurrency-async`; a bare BUILD task gets `tdd`; a task that matches nothing gets
+  no section at all, because a padded section teaches the model to skip it.
+- **`src/core/skills.ts`** — skill loading, header parsing and matching, resolved from the package so
+  it works in an install with no project setup.
+- **`src/core/skillsAudit.ts`** — pi's validation rules, reproduced strictly enough that a clean
+  audit means a clean start. Also catches what pi does not: a duplicate name (pi keys skills by name,
+  so one silently ceases to exist), a mistyped phase, a missing `kind`, and a name that disagrees
+  with its filename.
+- **A `package` E2E scenario** — `npm pack`, extracted and inspected. Every bug it looks for was
+  found by a user after install and by nothing in this repository: a file pi rejects, a symlink out
+  of the tree, a module the extension imports that npm did not publish, a UTF-8 BOM. The repo working
+  tree is not the product; the tarball is.
+- **A reachability guard.** "The tested code was not the shipped code" was this project's worst bug.
+  The `package` scenario now also walks every import from the extension entry point and fails on any
+  *new* module that ships without a path to it. Nine modules are unreachable today — `worker`,
+  `unstuck`, `review`, `rework`, `replan`, the three `goal*` modules and the audit itself — and they
+  are named in the test with the reason, so the debt is visible and cannot grow quietly.
+
+### Changed
+
+- `prototype` now leads with PLAN rather than BUILD — it answers a design question before you commit
+  to one, and the phase a skill leads with is what decides its rank.
+- Tag matching tolerates plurals, so a task about "two workers" matches the `worker` tag.
+
+---
+
 ## [2.0.0] — 2026-08-23
 
 Renamed from `pi-harness` to **infinity-harness**, and rebuilt from a working prototype into

package/README.md

@@ -186,6 +186,32 @@ verdict. It refreshes itself every 5 seconds and reconnects with backoff if the
 The dashboard is strictly read-only and binds to `127.0.0.1`. It never writes, and never bumps
 `baseRevision` — opening it can't perturb the run you're watching.
 
+## Craft skills
+
+28 short documents on how to do the work well — how to write a test worth
+keeping, how to debug something intermittent, how to design a module boundary.
+They ship with the package, so pi loads them wherever it's installed and the
+model can invoke any of them by name.
+
+A model with 28 skills available and no idea which one applies reads none of
+them, so **the brief names the ones that match the work in hand**. Each skill
+declares what it's for:
+
+```yaml
+kind: domain                                     # process | domain | meta
+phases: [plan, build, verify]                    # the phase it leads counts most
+tags: [concurrency, race, lock, mutex, deadlock] # vocabulary a task would use
+```
+
+A `process` skill belongs to its phase — TDD is the right answer for a BUILD
+task whatever the task says. A `domain` skill has to share vocabulary with the
+task: nobody needs the database skill because they happen to be in BUILD. So a
+task called *"serialise plan writes so two workers can't race on the lock"*
+gets `concurrency-async`, and a bare BUILD task gets `tdd`.
+
+When nothing matches, the brief has no skills section. An empty section is
+honest; a padded one teaches the model to skip it.
+
 ## Model routing (optional)
 
 Send cheap tasks to a small model and hard ones to a large one. Pick them with `/infinity:config` →
@@ -229,6 +255,7 @@ infinity-harness/
 ├── src/
 │   ├── core/                      types · paths · fsx · config · phases · gates · brief
 │   │                              · featureList (the SSOT) · lock · exec
+│   │                              · skills (match) · skillsAudit (guard)
 │   ├── ui/                        theme · widget (terminal) · dashboard (web)
 │   ├── loop.ts                    the continuous-run driver and its stop conditions
 │   ├── taskList.ts                atomic plan editor
@@ -242,8 +269,8 @@ infinity-harness/
 │   ├── config.json                pipeline state and settings
 │   ├── model-router.json          optional routing
 │   ├── docs/                      architecture · decisions · phase and role docs
-│   └── skills/                    29 craft skills the brief points at
-├── tests/                         20 files, plain node:assert
+│   └── skills/                    28 craft skills the brief points at
+├── tests/                         22 files, plain node:assert
 └── scripts/run-tests.mjs
 ```
 
@@ -255,7 +282,7 @@ there is one implementation, and the adapter calls it.
 ```bash
 npm install
 npm run check    # tsc --noEmit
-npm test         # 20 test files
+npm test         # 22 test files
 npm run e2e      # end-to-end against a live model
 ```
 

package/harness/docs/ARCHITECTURE.md

@@ -153,7 +153,7 @@ Every stop carries a reason. A human coming back finds an explanation, not a mys
 ## Verification
 
 - `npm test` — 20 unit files, plain `node:assert`, no framework.
-- `npm run e2e` — 11 scenarios over real temp projects, real git repos, real child processes: the
+- `npm run e2e` — 12 scenarios over real temp projects, real git repos, real child processes: the
   full pipeline walkthrough, loop convergence, every stop condition, SIGKILL-and-restart, a 6-way
   concurrent write fan-out with an unlocked control, data round-trip, the dashboard, widget
   rendering across shapes, adversarial input, and the extension adapter itself.

package/harness/docs/skills.md

@@ -0,0 +1,89 @@
+<!--
+Kept in docs/, not in harness/skills/.
+
+pi loads every .md in a declared skills directory as a skill and requires
+`name` and `description` frontmatter on each. A README has neither, so leaving
+it beside the skills made pi print a skill conflict on every start.
+`tests/skills.test.ts` now fails if anything in harness/skills/ would do that.
+-->
+
+# Craft Skills
+
+How to do the work WELL — the engineering discipline behind each pipeline
+phase. The phase docs (`harness/docs/phases/`) say *what* to produce; these
+skills say *how* an expert produces it.
+
+They ship with the package, so pi loads them wherever it is installed: the
+model can invoke any of them by name, and `/skill:<name>` lists them.
+
+**The brief names the ones that match the work in hand.** Each skill declares
+what it is for, so the brief can route:
+
+```yaml
+kind: domain                                    # process | domain | meta
+phases: [plan, build, verify]                   # leading phase counts most
+tags: [concurrency, race, lock, mutex, deadlock] # vocabulary a task would use
+```
+
+- **`process`** — how to work in a phase. Belonging to the phase is enough;
+  TDD is the right answer for a BUILD task whatever the task says.
+- **`domain`** — a subject area. Surfaces only when the task shares its
+  vocabulary. Nobody needs the database skill for being in BUILD.
+- **`meta`** — growing the toolkit. Vocabulary only, never a phase.
+
+Read the one the brief names before you start. Each is short, and it changes
+what you do.
+
+## Process skills
+
+| Skill | Leads | One-liner |
+|-------|-------|-----------|
+| `grilling.md` | DEFINE | Stress-test the spec with relentless questions |
+| `domain-modeling.md` | DEFINE | Pin down domain terms before writing code |
+| `research.md` | DEFINE | Answer questions from primary sources only |
+| `planning-tasks.md` | PLAN | Break specs into tracer-bullet vertical slices |
+| `codebase-design.md` | PLAN | Design deep modules behind small interfaces |
+| `prototype.md` | PLAN | Throwaway code that answers a design question |
+| `tdd.md` | BUILD | Red → green loop; tests worth keeping |
+| `self-review.md` | BUILD | The pass that runs before every validate |
+| `diagnosing-bugs.md` | VERIFY | Build a feedback loop before hypothesising |
+| `code-review.md` | REVIEW | Two-axis review: standards + spec |
+| `resolving-merge-conflicts.md` | any | Resolve conflicts by original intent |
+| `context-hygiene.md` | any | Externalise discoveries the moment they happen |
+| `scope-discipline.md` | any | The contract is the boundary; park everything else |
+| `stuck-protocol.md` | any | Stop thrashing, escalate cleanly |
+
+## Domain skills
+
+Matched by vocabulary, not by phase:
+
+`databases` · `http-apis` · `auth-security` · `frontend-ui` ·
+`testing-infra` · `concurrency-async` · `performance` ·
+`error-handling-logging` · `config-and-secrets` · `cli-design` ·
+`pi-todo-adapted`
+
+## Meta skills
+
+| Skill | Purpose |
+|-------|---------|
+| `capability-acquisition.md` | HAVE → ACQUIRE → CREATE → KEEP |
+| `writing-skills.md` | How to author a skill worth keeping |
+| `building-tools.md` | Standards for a project script anyone can run |
+
+Growing the library is part of the job. A skill you write into
+`.pi/skills/<name>.md` is loaded by pi on the next start — there is nothing to
+register — and committing it means the next session starts one rung higher.
+
+## Adding one here
+
+Frontmatter is a strict subset: `key: value`, `key: [a, b]`, `key: { k: v }`.
+No block scalars, no multi-line values. `name` must match the filename, be
+lowercase `a-z0-9-`, and `description`, `kind` and `phases` must all be
+present and valid — `npm test` enforces every one of those, because pi only
+warns and it warns on every single start.
+
+## Attribution
+
+Skills marked "Adapted from mattpocock/skills" derive from
+[Matt Pocock's skills repository](https://github.com/mattpocock/skills)
+(MIT License, © 2026 Matt Pocock), adapted for the infinity-harness pipeline.

package/harness/skills/auth-security.md

@@ -4,6 +4,7 @@ description: Authentication, authorization, secrets, and the injection/XSS/CSRF
 tags: [auth, authentication, authorization, security, login, password, token, jwt, session, oauth, secret, csrf, xss, injection, permission]
 when: task touches login, sessions, tokens, permissions, user input, or secrets
 phases: [plan, build, verify]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/building-tools.md

@@ -1,60 +1,56 @@
 ---
 name: building-tools
-description: Project tool standards — idempotent, self-documenting, non-interactive executables
-tags: [meta, tool, script, cli, automation, executable]
-when: a repeatable action deserves a registered executable instead of ad-hoc shell
+description: Project script standards — idempotent, self-documenting, non-interactive executables
+tags: [meta, tool, script, cli, automation, executable, makefile]
+when: a repeatable action deserves a script instead of the same shell dance twice
 phases: []
+kind: meta
 provenance: { origin: built-in }
 ---
 
 # Building Tools
 
-A tool is a registered executable under `harness/tools/` that future
-sessions (and other agents) can find and run. Build one when you catch
-yourself doing the same multi-step shell dance twice.
+Build one when you catch yourself doing the same multi-step shell dance
+twice. The bar is not "it worked once on my machine" — an unattended agent
+will run this at 3am with no one watching.
 
-## Process
+There is nothing to register. A script in the repo, named in `AGENTS.md` or
+`package.json`, is discoverable by the next session; a script nobody can
+find is a script nobody runs.
 
-1. `infinity-harness capability create tool <name>` → stub at
-   `harness/tools/<name>.sh` (any language works — .mjs, .py; the stub is
-   bash).
-2. Implement to the standards below.
-3. Register:
-
-   ```
-   infinity-harness capability add tool harness/tools/<name>.sh \
-     --run "bash harness/tools/<name>.sh" \
-     --tags db,fixtures --description "Reset local db to fixtures"
-   ```
-
-## Standards (the registration bar)
+## Standards
 
 - **Idempotent** — running it twice is safe and converges to the same state.
-- **`--help` works** — prints usage + purpose, exits 0. (`capability
-  doctor` checks exactly this.)
-- **`--json` where output is consumed** — machine-readable when another
-  tool or agent reads the result.
-- **Exit codes:** 0 success · 1 operation failed · 2 usage error.
-- **Never interactive** — no prompts, no confirmations; flags only. An
-  unattended agent runs this at 3am.
-- **Fail loud and specific** — errors name the thing that's wrong and the
-  likely fix, on stderr.
-- **Self-contained** — resolve paths relative to the project root, not the
-  caller's cwd.
+- **`--help` works** — prints usage and purpose, exits 0. This is the first
+  thing anyone runs, human or model.
+- **`--json` where output is consumed** — machine-readable when something
+  downstream reads the result. Humans get the summary line.
+- **Exit codes** — `0` success · `1` the operation failed · `2` you were
+  called wrong. An agent branches on these; get them right.
+- **Never interactive** — no prompts, no confirmations, no "are you sure".
+  Flags only.
+- **Fail loud and specific** — errors name the thing that is wrong and the
+  likely fix, on stderr. "Error: 1" costs someone an hour.
+- **Self-contained** — resolve paths from the project root, not the
+  caller's cwd. Check prerequisites at startup and fail with the install
+  command.
 
 ## Anti-patterns
 
-- **The snowflake** — works only on the author's machine (hardcoded paths,
-  undeclared deps). Fix: check prerequisites at startup, fail with install
+- **The snowflake** — hardcoded paths, undeclared dependencies, works only
+  where it was written. Fix: check prerequisites first, fail with
   instructions.
 - **The chatterbox** — pages of output hiding the result. Fix: one summary
   line by default, `--verbose` for the rest.
-- **The mutation surprise** — destructive with no dry-run. Fix: anything
-  destructive gets `--dry-run` and defaults to showing what it would do.
+- **The mutation surprise** — destructive with no dry run. Fix: anything
+  destructive gets `--dry-run`, and says what it would do.
+- **The second source of truth** — a script that keeps its own copy of state
+  the project already stores. Fix: read the real file.
 
 ## Checklist
 
-- [ ] Idempotent (ran it twice to prove it)
-- [ ] `--help` exit 0; exit codes correct
-- [ ] Registered with ≥2 tags + description
-- [ ] `infinity-harness capability doctor --type tool` passes
+- [ ] Ran it twice; the second run was a no-op
+- [ ] `--help` exits 0 and explains the purpose
+- [ ] Exit codes are 0 / 1 / 2 and mean what they should
+- [ ] No prompt, no confirmation, no TTY assumption
+- [ ] Named somewhere a cold reader will find it

package/harness/skills/capability-acquisition.md

@@ -4,6 +4,7 @@ description: The capability ladder — HAVE, ACQUIRE, CREATE, KEEP — for skill
 tags: [meta, capability, acquire, search, skill, mcp, tool, ladder, library]
 when: a task needs knowledge, system access, or an executable the project lacks
 phases: []
+kind: meta
 provenance: { origin: built-in }
 ---
 

package/harness/skills/cli-design.md

@@ -4,6 +4,7 @@ description: Command-line tool design — argument conventions, output contracts
 tags: [cli, command, terminal, flags, arguments, stdout, stdin, shell, script, tool]
 when: task builds or extends a command-line interface
 phases: [plan, build]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/code-review.md

@@ -4,6 +4,7 @@ description: Two-axis review (spec fidelity + standards/smells) with the Fowler
 tags: [review, quality, smell, refactor, standards, spec, diff, audit]
 when: reviewing a diff, a branch, or the whole delivery before shipping
 phases: [review, simplify]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/codebase-design.md

@@ -4,6 +4,7 @@ description: Deep modules — small interfaces hiding lots of behavior, seams, t
 tags: [design, architecture, module, interface, seam, refactor, coupling, abstraction, api]
 when: designing module boundaries, planning features, refactoring for clarity
 phases: [plan, simplify]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/concurrency-async.md

@@ -4,6 +4,7 @@ description: Concurrency and async correctness — races, idempotency, queues, c
 tags: [concurrency, async, race, parallel, queue, lock, mutex, retry, idempotent, worker, thread, promise, deadlock, atomic]
 when: task involves parallel work, background jobs, shared state, or retried operations
 phases: [plan, build, verify]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/config-and-secrets.md

@@ -4,6 +4,7 @@ description: Configuration discipline — env-driven config, validation at boot,
 tags: [config, configuration, environment, env, secret, settings, deploy, dotenv, variable]
 when: task adds configuration, environment handling, or deployment settings
 phases: [build, ship]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/context-hygiene.md

@@ -4,6 +4,7 @@ description: Externalize state before it decays — write discoveries down, re-r
 tags: [meta, context, memory, handoff, session, notes, playbook]
 when: any long session, and always before ending one
 phases: []
+kind: process
 provenance: { origin: built-in, notes: frontier-playbook }
 ---
 

package/harness/skills/databases.md

@@ -4,6 +4,7 @@ description: Relational database craft — schema design, migrations, transactio
 tags: [database, db, sql, postgres, postgresql, mysql, sqlite, schema, migration, transaction, index, query, orm, persistence, storage]
 when: task touches persistent data, schemas, queries, or migrations
 phases: [plan, build, verify]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/diagnosing-bugs.md

@@ -4,6 +4,7 @@ description: Feedback-loop-first debugging discipline for hard bugs and regressi
 tags: [debug, debugging, bug, error, failure, crash, flaky, slow, performance, regression, bisect]
 when: something is broken, throwing, failing intermittently, or slow
 phases: [verify, build]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/domain-modeling.md

@@ -4,6 +4,7 @@ description: Pin down domain terminology — glossary discipline and decision re
 tags: [domain, glossary, terminology, naming, model, ubiquitous, language, adr, decision]
 when: defining specs, resolving fuzzy or conflicting terms, recording decisions
 phases: [define, plan]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/error-handling-logging.md

@@ -4,6 +4,7 @@ description: Error taxonomy, fail-loud handling, structured logging that debugs
 tags: [error, exception, logging, log, observability, retry, crash, handling, monitoring, trace]
 when: task defines error paths, adds logging, or hardens failure behavior
 phases: [build, verify]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/frontend-ui.md

@@ -4,6 +4,7 @@ description: Frontend craft — state discipline, componentization, accessibilit
 tags: [frontend, ui, component, react, vue, svelte, state, form, accessibility, a11y, css, browser, render]
 when: task builds or changes user interface
 phases: [plan, build]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/grilling.md

@@ -4,6 +4,7 @@ description: Stress-test a spec or plan with relentless one-at-a-time questions
 tags: [grill, spec, requirements, questions, stress, interview, scope, clarify]
 when: before proposing the sprint contract, or when a plan feels underspecified
 phases: [define]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/http-apis.md

@@ -4,6 +4,7 @@ description: HTTP/REST API design — resources, status codes, errors, versionin
 tags: [api, http, rest, endpoint, route, json, status, error, versioning, pagination, webhook, request, response]
 when: task designs or implements HTTP endpoints or consumes external APIs
 phases: [plan, build]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/performance.md

@@ -4,6 +4,7 @@ description: Performance work — measure first, fix the biggest cost, cache wit
 tags: [performance, slow, latency, profiling, optimize, cache, memory, benchmark, throughput, speed]
 when: something is slow, memory-hungry, or a task sets performance targets
 phases: [verify, build]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/pi-todo-adapted.md

@@ -4,6 +4,7 @@ description: "Atomic infinity_plan pattern with omission deletion, baseRevision
 tags: [harness, pi-todo, atomic, baseRevision, omission, deletion, compaction, widget, task-list, dependency]
 when: "implementing infinity_plan, atomic revisioning, Pi widget with session persistence or task dependencies"
 phases: [build, verify]
+kind: domain
 provenance: { origin: "https://github.com/99percentpeople/pi-extensions", license: MIT, adapted: true, url: "https://github.com/99percentpeople/pi-extensions", contentHash: abf626df6a74a6fb }
 ---
 

package/harness/skills/planning-tasks.md

@@ -4,6 +4,7 @@ description: Break specs into tracer-bullet vertical slices with checkable accep
 tags: [plan, planning, slice, ticket, decompose, criteria, backlog, breakdown, refactor]
 when: writing or restructuring the feature list from a spec
 phases: [plan]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/prototype.md

@@ -3,7 +3,8 @@ name: prototype
 description: Throwaway code that answers a design question fast, then gets deleted
 tags: [prototype, spike, experiment, explore, poc, throwaway, design]
 when: a state model, logic shape, or UI direction cannot be judged on paper
-phases: [build, plan]
+phases: [plan, build]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/research.md

@@ -4,6 +4,7 @@ description: Answer factual questions from primary sources; capture cited findin
 tags: [research, docs, documentation, investigate, source, facts, api, spec, evidence]
 when: a factual question about an API, library, protocol, or tool blocks progress
 phases: [define, plan, build]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/resolving-merge-conflicts.md

@@ -4,6 +4,7 @@ description: Resolve git merge/rebase conflicts by original intent, verify, and
 tags: [git, merge, rebase, conflict, branch, hunk]
 when: an in-progress git merge or rebase has conflicting hunks
 phases: []
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/scope-discipline.md

@@ -4,6 +4,7 @@ description: The contract is the boundary — park ideas, resist drive-by fixes,
 tags: [meta, scope, creep, contract, focus, discipline, playbook]
 when: mid-task ideas, adjacent problems, or "while I'm here" temptations appear
 phases: []
+kind: process
 provenance: { origin: built-in, notes: frontier-playbook }
 ---
 

package/harness/skills/self-review.md

@@ -4,6 +4,7 @@ description: Structured pass before claiming done — criteria re-check, real ru
 tags: [meta, review, verify, done, quality, check, playbook]
 when: before running validate on any task — every time
 phases: [build, verify, simplify]
+kind: process
 provenance: { origin: built-in, notes: frontier-playbook }
 ---
 

package/harness/skills/stuck-protocol.md

@@ -4,6 +4,7 @@ description: What to do after repeated failures — stop, write down, reframe on
 tags: [meta, stuck, retry, failure, escalate, blocked, playbook]
 when: the same step has failed 2-3 times, or you notice you are looping
 phases: []
+kind: process
 provenance: { origin: built-in, notes: frontier-playbook }
 ---
 

package/harness/skills/tdd.md

@@ -4,6 +4,7 @@ description: Red → green test-driven loop — what a good test is, seams, anti
 tags: [tdd, test, testing, unit, integration, red-green, seam, mock, coverage]
 when: implementing any BUILD task, or fixing a bug that needs a regression test
 phases: [build, verify]
+kind: process
 provenance: { origin: "mattpocock/skills", license: MIT, adapted: true }
 ---
 

package/harness/skills/testing-infra.md

@@ -4,6 +4,7 @@ description: Test infrastructure — fixtures, isolation, flaky-test policy, CI
 tags: [test, testing, fixture, ci, flaky, coverage, mock, isolation, pipeline, suite]
 when: task sets up test tooling, fixtures, CI, or fights slow/flaky suites
 phases: [build, verify]
+kind: domain
 provenance: { origin: built-in }
 ---
 

package/harness/skills/writing-skills.md

@@ -4,6 +4,7 @@ description: How to author a skill worth keeping — scope, structure, frontmatt
 tags: [meta, skill, writing, author, documentation, checklist]
 when: creating a new skill or adapting an acquired one
 phases: []
+kind: meta
 provenance: { origin: "mattpocock/skills writing-great-skills", license: MIT, adapted: true }
 ---
 
@@ -54,7 +55,7 @@ Frontmatter uses a strict subset: `key: value`, `key: [a, b]`,
 
 ## Checklist
 
-- [ ] Frontmatter passes: `infinity-harness capability add skill <path>` (it validates)
+- [ ] Frontmatter is complete: `name` matching the filename, `description`, `kind`, `tags`, `when`, `phases`
 - [ ] A cold reader knows exactly what to do and how to check they did it
 - [ ] Every rule is checkable; every anti-pattern has a fix
 - [ ] Attribution line present if adapted from elsewhere

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "infinity-harness",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "A pi agent extension that runs a gated build pipeline unattended \u2014 enforces phases, validates with deterministic gates, and keeps working for hours or days without losing the plan.",
   "type": "module",
   "keywords": [