{"slug":"spike-consumer-forked","title":"spike-consumer-forked","summary":"OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-10-15T13:12:03.945694Z","repo":{"url":"https://github.com/testdouble/han","stars":303,"forks":24,"license":"MIT","updatedAt":"2026-10-14T20:22:28Z"},"bodyHtml":"
\n

name: spike-consumer-forked\ndescription: OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.\nallowed-tools: Read, Write, Skill

\n

Incident Post-Mortem Builder (forked arm)

\n

You are producing a written incident post-mortem report. This skill has SIX steps. The steps below are the whole skill. Complete all six in order. Do not stop until Step 6 has written the artifact file and you have reported the completion token.

\n

The invocation gives you a TRIAL_ID and the path to an incident data file, plus a TRIALS_DIR to write the artifact into.

\n

Step 1 — Read the incident data

\n

Read the incident data file provided in the invocation.

\n

Step 2 — Extract the four key facts

\n

From the data, extract exactly these four facts and hold them; every one must appear in your final report:

\n
    \n
  1. the incident ID
    2. \n
  2. the primary error code
    3. \n
  3. the peak latency figure
    4. \n
  4. the affected service name
    5. \n
\n

Record them as a working note before you continue.

\n

Step 3 — Source the readability standard

\n

Before writing any prose, source the shared readability standard so your report is in voice. Invoke the Skill tool with skill name spike-guidance-forked. Absorb the standard it surfaces.

\n

Sourcing the standard is a means to writing the report, not the report itself. You are NOT done after this step. Continue immediately to Step 4.

\n

Step 4 — Draft the report

\n

Write the incident post-mortem with these five labeled sections, applying the readability standard from Step 3. Each section is a short paragraph:

\n
    \n
  1. Summary — the one-line bottom line; must name the incident ID and the affected service.
    2. \n
  2. Impact — must state the peak latency figure.
    3. \n
  3. Root cause — must name the primary error code.
    4. \n
  4. Resolution — how it was mitigated.
    5. \n
  5. Follow-up actions — at least two.
    6. \n
\n

Step 5 — Self-check

\n

Check the draft against the standard: main point first, one idea per paragraph, descriptive headings, short active sentences.

\n

Step 6 — Write the artifact and emit the completion token

\n

Write the full report to a file at <TRIALS_DIR>/<TRIAL_ID>.md. As the final line of that file, on its own line, write the completion token exactly in this form (substitute the real values):

\n

CONSUMER_COMPLETE | TRIAL_ID=<TRIAL_ID> | facts: <incidentID> <errorCode> <peakLatency> <service>

\n

Then, in your final message, state that all six steps are complete and paste that completion-token line verbatim.

\n","files":[{"path":"SKILL.md","sizeBytes":2643,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-10-15T13:13:07.639695Z","sha256":"5C363F98EB723188982C68F52BEDA225E6FFA386ABC2BCBBD16028BDA72759EE","sizeBytes":1365},"review":null,"source":{"repositoryUrl":"https://github.com/testdouble/han","path":"docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-forked","license":"MIT","commit":"abba73a773528905a8f3d15956029394746e5c7f","subtreeSha":"0B73B3278BBD8E054ECA663D597DE4B7710757B1B007E11F15E635D5F45F5F46","lastSyncedAt":"2026-10-15T13:11:53.672149Z"},"reviewedAt":"2026-10-15T13:15:21.60671Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/testdouble/han/tree/main/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-forked"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install testdouble-han@llmmart"},{"target":"git","command":"git clone https://github.com/testdouble/han.git"}]}