harness-core plugin

What's inside harness-core

5 parts read from the plugin's own files.

Skills in harness-core

1. 
   decision-log3xachris/3xa-harness

   Keep one append-only log where decisions, rejections, and corrections survive a context reset — each entry carrying a fixed index line a later session can search, and pointing at where the full detail lives instead of copying it. Read it first when picking up a project you have no memory of; write to it when recording why something was chosen or dropped, when handing over to a fresh session or another agent, or when answering "why did we do it this way" months later.

   2 files
   17stars
2. 
   handoff3xachris/3xa-harness

   Write one snapshot of the current state, organized by what the next reader needs rather than by what this session did, so a person or session with zero memory of the work can read it once and keep going — every open thread's status, every already-spent asset and how to start it, every cross-thread dependency, every unresolved debt, each answered or marked none. Use when a session is ending, a task is moving to another person or agent, a long break is coming, or a fresh session needs to inherit in-flight work without whoever was here to fill the gaps.

   2 files
   17stars
3. 
   honest-closeout3xachris/3xa-harness

   Close a task with a report a reviewer can trust — every acceptance line answered with evidence or a recorded blocking reason, human corrections credited to whoever made them, refuted hypotheses kept, background processes proven stopped, and the chat message copied verbatim from the report. Use when reporting work as finished, writing a completion report, summarising what a session achieved, or handing a result to whoever reviews it.

   2 files
   17stars
4. 
   sensory-gate3xachris/3xa-harness

   Hand images, audio, video, or any artifact only a human eye or ear can judge to a human, in one batch, and hold there until an identified reviewer records the approved batch scope — rejections made by dragging a file into a rejects folder. Use when producing renders, generated art, TTS or voice output, edited video, or anything whose acceptance rests on "does this look or sound right".

   2 files
   17stars
5. 
   workorder3xachris/3xa-harness

   Freeze a task's scope into a written order before building, then run it to done in one pass — build, self-verify, self-fix, re-verify — closing with a passing result or a two-strike failure trail. Use when a task spans more than a few steps, when scope is drifting mid-build, when a request is too vague to start from, or when handing work to a subagent.

   2 files
   17stars