hash-id
- 10 skills
- 0 followers
- 13 hours ago last updated
- ▌ Hrt Artifact Lint · hash-id bundleRuns the deterministic structural lint over a tempa-spec change's artifacts (hashtag counts, checkbox format, delta headers, capability<->spec-file correspondence, Covers: target existence, design.md section presence, unverified External Dependencies rows) so a language model does not do this by hand. Called from hrt-adversarial-authoring and hrt-align-consistency-review. Judgement checks stay with the reviewers.
- ▌ Hrt Change Size Gate · hash-idChange-size check run inside the tempa-spec schema's `proposal` phase, before the "What Changes" list is finalized. Detects when a draft bundles several independent changes that each deserve their own change, stops and asks the user whether to split (default: one change; the agent never splits on its own), and when the user splits, records the deferred slices in proposal.md's Out of Scope section, discovery.md's Key Decisions, and openspec/BACKLOG.md. Rationale is in docs/research/2026-08-27-mattpocock-skills-gate-and-seams.md.
- ▌ Hrt Dark Mode Opt In · hash-idOpt-in gate for tempa-spec's dark mode (bounded autonomous decision-making across discovery-through-align, optionally through apply). Never offered proactively - only activates when the user asks for it unprompted, in their own words. Shows a mandatory risk warning before any confirmation, then asks which variant (planning-only or +implementation) and creates dark.md. Use once, at or after discovery, only on explicit user request.
- ▌ Hrt Apply Code Review · hash-idCode-vs-artifacts review for OpenSpec's tempa-spec schema — checks implemented code against specs/**/*.md, design.md, and tasks.md once every task is complete. A loop of up to 3 passes, each run in a fresh subagent session with no memory of the implementer, HIGH/MEDIUM/LOW severity with MECHANICAL/DECISION resolution tagging, hard-gated on passing tests and lints. Use during the tempa-spec schema's `apply` Phase 2 review.
- ▌ Hrt Backlog Reconcile · hash-idUser-invoked maintenance for openspec/BACKLOG.md. Reconciles deferred-slice entries against the shipped specs in openspec/specs/, proposes deleting entries now covered, and edits the file only on the user's per-entry confirmation. Not part of the tempa-spec pipeline. Run it by hand, ideally right after openspec archive.
- ▌ Hrt Dark Mode Routing · hash-idSingle source of truth for where an escalation-worthy finding goes when tempa-spec's dark mode is active (dark.md exists). Each of proposal, specs, design, align, and apply points here instead of inlining its own dark-mode carve-out. Says which findings route to hrt-dark-mode-decision-gate, which still go to the user, and which dark.md section records the result.
- ▌ Plain Language Writing · hash-idTwo writing rule sets for readers who may not read English fluently: COMMS for live agent-to-user text (interview questions, confirmations, blockers), ARTIFACT for persistent artifact prose (discovery.md, proposal.md, specs, design.md). A caller states which set applies. Evidence backing is in docs/research/2026-08-07-plain-language-non-native-readers.md.
- ▌ Hrt Adversarial Authoring · hash-idAuthor-then-adversarial-review authoring pass for a single OpenSpec artifact — a subagent drafts it, `hrt-artifact-lint` clears the deterministic structure checks, then two subagents review it concurrently in fresh isolated contexts (a Destructive Critic for content/logic, a Structural Auditor for the structural judgement calls a linter cannot make), findings resolved before finalizing. Parameterized by artifact (proposal, specs, or design). Use during the tempa-spec schema's `proposal`, `specs`, and `design` phases.
- ▌ Hrt Dark Mode Decision Gate · hash-idSteel-manning resolution for tempa-spec's dark mode. Resolves findings that would normally escalate to the user (DECISION/HIGH from hrt-align-consistency-review and hrt-apply-code-review; single-reviewer UNANCHORED from hrt-adversarial-authoring). Always a fresh subagent. Use only when dark.md exists and the calling skill has a finding it cannot resolve on its own evidence.
- ▌ Hrt Align Consistency Review · hash-idCross-artifact consistency review for OpenSpec's tempa-spec schema — checks discovery.md, proposal.md, specs/**/*.md, design.md, and tasks.md are mutually consistent and faithful to the requirements, BEFORE any code is written. One cycle is an ALIGN pass (deterministic structure via `hrt-artifact-lint`, then a consequence gate, then HIGH/MEDIUM/LOW × MECHANICAL/DECISION — LOW DECISION findings batched, not surfaced one at a time), a fresh-context VERIFY pass (skipped when ALIGN and the lint were both clean), then a human WALKTHROUGH; walkthrough feedback re-enters ALIGN. Exits on a clean walkthrough round or user sign-off; after 3 cycles it asks whether to keep going. Use during the tempa-spec schema's `align` phase.