haiku

A workflow method for guiding coding work through stages, with role-based tasks, completion rules, and preserved context between steps.

In plain words
What is it for?
Use it to organise a task lifecycle, switch between defined working roles, check completion criteria, and retain context.
Why use it?
It provides a repeatable structure for long or multi-step work and helps keep important context from being lost.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add gigsmart/haiku-method
agentmods
npx agentmods add plugins/gigsmart/haiku-method/marketplace
Clone the repo
git clone --depth 1 https://github.com/gigsmart/haiku-method

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

haiku scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/marketplace.json · 35 lines

What it actually says

{
  "name": "haiku",
  "owner": {
    "name": "GigSmart",
    "url": "https://gigsmart.com"
  },
  "plugins": [
    {
      "name": "haiku",
      "description": "H·AI·K·U methodology — universal lifecycle orchestration with hat-based workflows, completion criteria, and automatic context preservation.",
      "source": {
        "source": "npm",
        "package": "haiku-method"
      },
      "category": "Pattern",
      "keywords": [
        "haiku",
        "haiku-method",
        "lifecycle",
        "orchestration",
        "methodology",
        "workflow",
        "iteration",
        "completion-criteria",
        "hat-switching",
        "context-preservation",
        "human-ai-collaboration"
      ]
    }
  ],
  "metadata": {
    "version": "10.3.0"
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 35 lines scan A fc2838c76110

Subscribe to this mod's changes

haiku is a plugin published in the GitHub repository gigsmart/haiku-method (24 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.