Explains Jack Wotherspoon's Humans vs Slop talk and helps create quality gates for AI-heavy software work: review-cost analysis, slop detection heuristics, durable-value metrics, and human-judgment checkpoints. Use when the user asks about AI-generated maintenance burden, review economics, or preserving taste in…
Generate closure-grade HE eval and drift proof for one execution slice. Use when Linear, milestone, or source-prompt closure needs validation evidence.
Convert approved HE cognition into small live-ready Linear execution tracking. Use when strategy, reframe, plan, bug, or source-prompt evidence needs scoped issue, milestone, or project routing with explicit confirmation before any live mutation.
Routes old phase-heartbeat requests into HE phase work: check the approved plan, reuse or create a 10-minute continuation only with authority, run phase gates, delegate the active slice to he-work, and stop before commit or tracker closure. Use when a user says phase heartbeat, keep this PR moving, or continue phases.
Runs approved Harness Engineering plans in recurring phases: check live state, confirm continuation authority, execute only the active he-work slice, verify gates, update Linear only with approval, and stop before unsafe staging or closure. Use when a plan, issue, or PR needs continued phase-by-phase execution.
Create evidence-backed HE reframe migration programs. Use when structural drift, routing ambiguity, or source-prompt gaps need phased rollback-safe execution.
Create or refresh evidence-bound Harness Engineering learning artifacts from verified solved problems. Use when a fix worked, a repeated failure should become durable knowledge, or .harness/solutions and Project Brain need maintenance.
Compress HE cognition artifacts into evidence-backed strategy. Use when intent, review, triage, ADR, core, or source-prompt comparison evidence needs durable direction.
Use when hardening, converting, auditing, or pre-release checking a Codex plugin package by verifying manifest paths, bundled skills, hooks, MCP/app config, validation gates, and release blockers.
Route plugin-factory requests to the right lane. Use when plugin creation, building, installation, review, or routing is broad, mixed, or under-specified.
Reviews and improves SKILL.md packages by fixing audit findings, triggers, examples, evals, token budget, release proof, safety verdicts, comparator/baseline choices, and bounded code-lens hardening. Use when the user says improve a skill, fix a skill file, review SKILL.md, raise Tessl score, reduce context cost, add…
Analyzes Codex skill-management requests, selects the workflow lane, and returns selectedlane, mode, nextstep, and blockers. Use when the user says create a skill, add/update/fix/review a skill, install/sync/list skills, choose a workflow, or merge/retire a skill.
Analyze options and trade-offs before traceable work is ready, without pretending exploration is a plan. Use when the user wants options, alternatives, decision matrices, or a bounded ideation pass before trace planning.
Generate closure proof with exact commands, outcomes, artifact paths, untested lanes, and residual risk. Use when work and review need a receipt before closeout, release, tracker movement, or handoff.
Plan how to implement one approved slice, including file targets, validation gates, rollback, and proof lanes. Use when a slice spec is accepted and the user needs the implementation order before code changes.
Analyze stale or conflicting lifecycle state by separating local, PR, CI, review, tracker, artifact, and session truth. Use when status is confused, work resumed after drift, evidence lanes disagree, or a closeout claim may be stale.
Plan a stuck, stale, or unsafe frame into a smaller viable direction with rollback and decision boundaries. Use when a migration, plan, PR, or implementation path is producing churn, conflicting claims, or unsafe scope.
Create a durable guardrail, validator, doc, eval, or skill-reference update from a verified failure or learning. Use when the user asks to capture learning, prevent recurrence, encode review feedback, or refresh stale guidance.
Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers. Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification.
Create one selected trace or tracker slice spec with acceptance criteria, constraints, validation, and exit conditions. Use when exactly one slice has been selected and needs a buildable contract before implementation planning.
Plan traceable work bullets that connect intent, evidence, acceptance, and proof gaps. Use when an idea or reframe needs decomposition into traceable work units before tracker or slice specification.
Plan tracker-ready slices with dependencies, labels, acceptance fields, and validation placeholders. Use when trace work needs Linear-ready or tracker-ready issue structure without actually mutating the tracker.
Build only the approved slice while preserving scope, unrelated worktree changes, and validation evidence. Use when an approved execution plan or explicit bounded task is ready for implementation.
★not rated 8 10d agoA36 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: