Menu
Promote slice-local decision notes into durable repo docs. Uses the active plan's decision_record to decide between no-op, decision-ledger, or ADR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run PR-sized Harness Kit dogfood replay trials in temporary repos to validate HK lifecycle UX with realistic tasks and observe how agents naturally discover or misuse HK.
Mine repository validation contracts and propose or audit Harness Kit hk profiles. Use when choosing an hk profile, when no exact repo/module profile exists, when a user asks to create or update a custom profile, or when inspecting CI, hooks, mise, package scripts, repo docs, or HK config diagnostics to draft profile checks/reviews.
Router skill for Harness Kit config authoring and maintenance. Use when a user asks to create, audit, update, or repair HK profiles, system maps, target bindings, or dots/user-level harness.toml config. Delegates to profile and system-map authoring skills instead of duplicating their logic.
This skill creates, updates, audits, and validates Harness Kit system maps, including repo-local .harness/system.toml files and target-level user/dots system_map overlays. Use when authoring agent-facing component/invariant maps, connecting touched paths to relevant HK profile check labels, dogfooding system-map candidates, or preparing Harness Kit CLI integration trials.
This skill finds and attaches Pi, Claude Code, and Codex session or review transcripts to active Harness Kit work using `hk artifact attach`. Use when the user asks to capture agent sessions, attach transcripts, preserve Codex/Claude/Pi review evidence, or inspect HK lifecycle artifacts.
Skill-first workflow for planning, implementing, reviewing, and handing off a meaningful repo slice. Use when starting a slice, rendering planner/implementer/ reviewer prompts with mise, deciding what evidence to keep, or evaluating prompt quality with holdout sample tasks.
| name | spec-sync |
| description | Promote slice-local decision notes into durable repo docs. Uses the active plan's decision_record to decide between no-op, decision-ledger, or ADR. |
| allowed-tools | Read, Edit, Write, Glob, Grep, Bash |
Prepare the repo for mise run spec-check.
The active plan stages decisions in DECISIONS.md. Durable records are then:
decision_record: none → keep the note slice-local onlydecision_record: ledger → append an entry to docs/explanation/decision-ledger.mddecision_record: adr → create or update an ADR under docs/explanation/decisions/SPEC.md, docs/explanation/architecture.md, and the active plan's DECISIONS.mdcontract_change and decision_recordSPEC.md if contracts/invariants changeddecision_recordWhere Reflected and Promotion sections so the
path from slice-local note to durable doc is obvious