Claude Skill

spike-guidance-forked

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download testdouble-han-docs_plans_han-communication-plugin_artifacts_oi-3-spike_harness-skills_spike-guidance-forked-abba73a.zip · 1 KB

testdouble/han 303 24 forks MIT Updated 18h ago

Part of testdouble/han — 47 skills

Install

skills CLI

npx skills add https://github.com/testdouble/han/tree/main/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-guidance-forked

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install testdouble-han@llmmart

Git git clone https://github.com/testdouble/han.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole testdouble/han collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Readability Guidance (forked variant)

You have invoked the readability-guidance skill to source the shared writing standard before you draft prose. Apply it while you draft, then RETURN to the workflow that called you — this guidance is a means to writing your deliverable, not the deliverable itself.

Emit the line SPIKE_GUIDANCE_MARKER_5R8_FORKED once, to confirm the guidance rendered, then continue.

The audience frame (drafting stage)

While drafting, write for a capable reader who did not do this work and lacks the author's context. This single instruction is the most practical lever for plain output: it steers away from insider shorthand, unstated assumptions, and the author's own mental model.

What the standard requires

Main point first. The opening line states the bottom line. A reader who stops after one sentence still gets the answer.
One idea per paragraph. Each paragraph carries one idea; its first sentence carries the weight.
Descriptive headings. Each heading names its content ("Why the request times out," not "Analysis").
Short, active sentences. Roughly fifteen to twenty words on average; few past twenty-five.
Common words. Prefer the common word over the technical synonym.
Numbered lists for steps, bullets for the rest.
Progressive disclosure. Reveal the core first and detail in layers.

Self-check criteria (post-draft stage)

After the draft exists, check: does the opening line state the main point? Does each paragraph carry one idea? Does each heading name its content? Any sentence past about thirty words is a candidate to split.

The standard is now surfaced into your context. Do not treat this guidance as your final answer. Proceed to the next step of the skill that invoked you and produce its deliverable.

Files (han)

SKILL.md 2.1 KB

---
name: spike-guidance-forked
description: OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.
allowed-tools: Read
context: fork
---

# Readability Guidance (forked variant)

You have invoked the readability-guidance skill to source the shared writing standard before you draft prose. Apply it while you draft, then RETURN to the workflow that called you — this guidance is a means to writing your deliverable, not the deliverable itself.

Emit the line `SPIKE_GUIDANCE_MARKER_5R8_FORKED` once, to confirm the guidance rendered, then continue.

## The audience frame (drafting stage)

While drafting, write for a capable reader who did not do this work and lacks the author's context. This single instruction is the most practical lever for plain output: it steers away from insider shorthand, unstated assumptions, and the author's own mental model.

## What the standard requires

- **Main point first.** The opening line states the bottom line. A reader who stops after one sentence still gets the answer.
- **One idea per paragraph.** Each paragraph carries one idea; its first sentence carries the weight.
- **Descriptive headings.** Each heading names its content ("Why the request times out," not "Analysis").
- **Short, active sentences.** Roughly fifteen to twenty words on average; few past twenty-five.
- **Common words.** Prefer the common word over the technical synonym.
- **Numbered lists for steps, bullets for the rest.**
- **Progressive disclosure.** Reveal the core first and detail in layers.

## Self-check criteria (post-draft stage)

After the draft exists, check: does the opening line state the main point? Does each paragraph carry one idea? Does each heading name its content? Any sentence past about thirty words is a candidate to split.

---

The standard is now surfaced into your context. Do not treat this guidance as your final answer. Proceed to the next step of the skill that invoked you and produce its deliverable.