What makes fix-plan notable?

2.3K downloads. Trust evidence available

How should fix-plan be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

fix-plan

fix_plan.md / checklist.md schema and lifecycle management. Topics — format ([ ]/[x]/[BLOCKED] markers, Progress/Completed sections), priority (P0-P3 BLOCKED suffix + external/selfable classification), add (Action/Why/How authoring), update (flip marker / note / `[KEY:VALUE]` attr), upsert (dup-check → update in place or fall back to add), draft (deferred plan stub → promote via code-workflow), move ([x] → Completed summary, subtree partial completion), sync (gh pr/issue state polling → auto-check), issue-drafts (write → publish → archive → delete), model-triage (fit + dedicated section), completion-criteria (DoD + marker rules). Default (no args): move (or archive-receiver) → format → sync → priority → flowchart-sync (incl. pinned-mission liveness check), scoped by role-profile (--role=pm|deep|impl). Use when: "fix_plan", "checklist", "BLOCKED priority", "triage blocked", "fix-plan sync", "issue draft cleanup", "fix-plan draft", "fix-plan default", "fix-plan archive", "model triage", "completion criteria", "role profile", "--role", "orca session launch", "fix-plan upsert", "dup check tracker", "pinned mission liveness", "pinned-backing", "set-attr".

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.3k

Updated

Oct 9, 2026

Version

0.17.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.3K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.3K downloadsadoption · observed Oct 9, 2026
Latest release: 0.17.1release · observed Oct 6, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17ay1v6v88r2m102pvvc44gz183qcrm:fix-plan

Install using `clawhub skill install s17ay1v6v88r2m102pvvc44gz183qcrm:fix-plan` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/drumrobot/fix-plan before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-drumrobot-fix-plan/snapshot"

Documentation

CLAWHUB

160,000 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: fix-plan
description: |
  fix_plan.md / checklist.md schema and lifecycle management. Topics — format ([ ]/[x]/[BLOCKED] markers, Progress/Completed sections), priority (P0-P3 BLOCKED suffix + external/selfable classification), add (Action/Why/How authoring), update (flip marker / note / `[KEY:VALUE]` attr), upsert (dup-check → update in place or fall back to add), draft (deferred plan stub → promote via code-workflow), move ([x] → Completed summary, subtree partial completion), sync (gh pr/issue state polling → auto-check), issue-drafts (write → publish → archive → delete), model-triage (fit + dedicated section), completion-criteria (DoD + marker rules).
  Default (no args): move (or archive-receiver) → format → sync → priority → flowchart-sync (incl. pinned-mission liveness check), scoped by role-profile (--role=pm|deep|impl).
  Use when: "fix_plan", "checklist", "BLOCKED priority", "triage blocked", "fix-plan sync", "issue draft cleanup", "fix-plan draft", "fix-plan default", "fix-plan archive", "model triage", "completion criteria", "role profile", "--role", "orca session launch", "fix-plan upsert", "dup check tracker", "pinned mission liveness", "pinned-backing", "set-attr".
metadata:
  author: es6kr
  version: "0.1.0"
depends-on:
  - code-workflow
  - github-flow
allowed-tools:
  - Read
  - Edit
  - Write
  - Grep
  - Bash(gh:*)
  - Bash(mv:*)
  - Bash(mkdir:*)
---

# Fix Plan

Schema and lifecycle management for `fix_plan.md` (Ralph convention) and `checklist.md` (non-Ralph workspaces). Vendor-agnostic — extracted from Ralph integration to be reusable across environments.

## Topics

| Topic | Description | Guide |
|-------|-------------|-------|
| add | New item authoring schema (Action / Why / How), length budget, deliverable separation (research / plan / checklist split) | [add.md](./add.md) |
| claim | Multi-session in-progress lease: `[CLAIMED:<sid>:<ts>]` suffix tag on `[ ]` / `[BLOCKED:*:selfable]` items, claim→refresh→release lifecycle, stale-TTL takeover — prevents two sessions duplicating the same item | [claim.md](./claim.md) |
| completion-criteria | Definition of done per item output type (`Why` = scope narrative vs `How to apply` = deliverable), marker transition rules, residual-scope split | [completion-criteria.md](./completion-criteria.md) |
| draft | Record a deferred plan **stub** (purpose + defer reason + resume trigger + expected deliverable) in `## Plan Drafts` when full planning is postponed; promote to `code-workflow` research→plan when the trigger fires. Invoked `/fix-plan draft` | [draft.md](./draft.md) |
| flowchart | Priority flowchart (Mermaid `graph TD` dependency graph) authoring, clean syntax rules (no inline `%%`), plan document node mapping (`llm-wiki/outputs/`, `.ralph/plan-drafts/`) without `file://` URLs, the `pm`-role default-pipeline sync procedure (drift check against priority-triage output), and the pinned-mission liveness check (`pinned_liveness_check.py` — cite backing items via `<!-- pi

_meta.json

{
  "ownerId": "kn74k8yfvftx6f062qa8fzyd8h8373jd",
  "slug": "fix-plan",
  "version": "0.17.1",
  "publishedAt": 1791273355701
}

add.md

# Add

New item authoring schema. Action / Why / How three-element format, length budget, deliverable separation rules.

## Item format (HARD STOP)

Every new fix_plan entry contains three required elements. Single-line action-only entries are forbidden.

```markdown
- [ ] {Action: imperative verb-form, one sentence}
  - **Why**: {motivation — purpose, background, intent in 1-2 sentences}
  - **How to apply**: {procedure / tools / verification approach}
  - {optional sub-steps, command examples, file paths}
```

### RAG pre-lookup gate (HARD STOP — context direction)

**Before adding or upserting an item, run a RAG (vector-memory) semantic search on the item's core keywords.** This gate answers a different question than the Canonical medium gate below: canonical-medium asks "is this tracker the record of truth?"; this gate asks "is there already known context on this topic?" Writing a new entry without checking prior context risks re-investigating a problem that a past session already diagnosed, or duplicating an item that already exists in a different phrasing.

1. **Search first**: run the skill domain's standard semantic-search script (e.g. `qdrant-search.py --semantic "<core keywords>" --limit 5`) before touching the tracker file's content. Prefer the domain's own script over an ad-hoc MCP call — see the workspace's tool-selection-priority rule (script/CLI first, MCP only when no script exists).
2. **Fold hits into the entry**: if the search surfaces prior diagnosis, an existing related item, or a linked plan/research document, reference it in the new entry's body (`**Why**` or a one-line sub-bullet) instead of re-deriving the same analysis from scratch.
3. **No hits is not skip-worthy evidence of anything but absence**: zero results means proceed with authoring normally — it does not excuse skipping the search itself.

#### Don't / Do

| # | Don't | Do |
|---|-------|-----|
| 1 | Read/edit the tracker file directly to add an item without running a semantic search on the item's topic first | Run the semantic search first, then open the tracker file to place the entry |
| 2 | Re-derive a diagnosis or procedure from scratch when the search surfaces a matching prior session's finding | Cite the prior finding (one-line pointer) and build on it instead of repeating the investigation |
| 3 | Treat the Canonical medium gate's pinned-header check as covering this | The two gates are independent axes — pinned-header answers "where does this belong", RAG search answers "what is already known about it". Both run, in either order relative to each other, but RAG search runs before the item body is drafted |

#### Self-check before drafting a new entry

1. Did you run a semantic search on the item's core keywords before drafting the entry body?
2. If the search returned relevant hits, does the entry body reference them (rather than silently ignoring them)?
3. If the search returned nothing, did you still author the entry normally rather than treating the e

CHANGELOG.md

# Changelog

## [0.17.1](https://github.com/es6kr/skills/compare/fix-plan-v0.17.0...fix-plan-v0.17.1) (2026-10-04)


### Bug Fixes

* **fix-plan:** add a general attribute slot to update_item ([#582](https://github.com/es6kr/skills/issues/582)) ([7610a95](https://github.com/es6kr/skills/commit/7610a95552136a7a29622b6b48c75830a24f765e))

## [0.17.0](https://github.com/es6kr/skills/compare/fix-plan-v0.16.1...fix-plan-v0.17.0) (2026-09-30)


### Features

* **fix-plan, consolidate:** consolidate task coordination, review collection, and docs ([d6162d8](https://github.com/es6kr/skills/commit/d6162d8d25bb80c85aa2c5cd475afdf0ee638535))
* **fix-plan:** add task lock, artifact scanner, prune, and cleanup utilities ([90c8d34](https://github.com/es6kr/skills/commit/90c8d342a0e56ab312b0b59473857ebc149fab1b))


### Bug Fixes

* **fix-plan:** enforce flowchart precedent, residual verification, and triage rules ([acea09d](https://github.com/es6kr/skills/commit/acea09dd37a62479ffd90e82e6fccdeadac2d5b4))
* **fix-plan:** make the task lock a real mutex and the tracker write atomic (green) ([4dc2f7e](https://github.com/es6kr/skills/commit/4dc2f7e433a0f6fa19fee5120c7b0ec58f49477c))

## [0.16.1](https://github.com/es6kr/skills/compare/fix-plan-v0.16.0...fix-plan-v0.16.1) (2026-09-27)


### Bug Fixes

* **fix-plan:** add [ASSIGNED:&lt;target&gt;] tag to claim.md for workspace-aware task assignment ([#555](https://github.com/es6kr/skills/issues/555)) ([8d3ad37](https://github.com/es6kr/skills/commit/8d3ad37245dc53bae748879f27bcd4db9dbcd72b))
* sync claude-memory refs to agent-memory-personal collection alias ([5f7fed1](https://github.com/es6kr/skills/commit/5f7fed113de84196df3a74688ea464b5c594d587))

## [0.16.0](https://github.com/es6kr/skills/compare/fix-plan-v0.15.0...fix-plan-v0.16.0) (2026-09-24)


### Features

* **fix-plan:** add hook-integrity source&lt;-&gt;cache reverse sync check ([77aa86b](https://github.com/es6kr/skills/commit/77aa86ba3f9b74a51c3ea02bb9fd0adb58b46660))
* **fix-plan:** add pipeline log and hook integrity check scripts ([e93a432](https://github.com/es6kr/skills/commit/e93a4323b54a311fcda6855163ffe14c2c146412))


### Bug Fixes

* **fix-plan:** add pinned-mission liveness check to flowchart-sync step ([#527](https://github.com/es6kr/skills/issues/527)) ([5c962a7](https://github.com/es6kr/skills/commit/5c962a71ffab690e3844855026ca21d0c141d968))
* **fix-plan:** add task allocation and channel dispatch stage to pm profile ([342a572](https://github.com/es6kr/skills/commit/342a5726a75da01467b4ada57d41dbd1df305136))
* **fix-plan:** carry k3s_workload through the v2 profile translation ([73e2994](https://github.com/es6kr/skills/commit/73e29949563689befe23c6f8f999fd8bff86664b))
* **fix-plan:** document the Pipeline Execution Log section and its writer scripts ([4b42a94](https://github.com/es6kr/skills/commit/4b42a948f9d5cbd06a7362b25c5f910eab783520))
* **git-repo:** add prune_merged_worktrees.py + 7 accumulated fixes ([3d2ee94](https://github.com/es6k

claim.md

# Claim — Multi-session In-progress Lease

Prevents two contexts — two interactive sessions, or an interactive session plus an autonomous Ralph loop / background dispatch — from independently working the same tracker item. A **claim** is a lightweight, self-expiring lease stamped onto an item the moment a session starts working it, so any concurrent reader sees the item is already in flight.

## Why

`fix_plan.md` / `checklist.md` are frequently edited by more than one context at once. The `[ ]` / `[x]` / `[BLOCKED]` markers describe an item's *state*, not *who is currently acting on it*. Without a claim, two sessions can both read a `[ ]` item, both decide it is available, and both do the same work — the exact duplicate-progress hazard this topic prevents.

A claim is **not** a new checkbox state. It is a concurrency annotation (a lease) that rides alongside the existing marker, orthogonal to pending / blocked / done.

## Marker syntax

Append a `[CLAIMED:<session>:<timestamp>]` suffix tag **after** the standard checkbox marker, before the item text:

```markdown
- [ ] [CLAIMED:84f9e320:2026-08-13T11:20] Recover Plane index 84 lines
- [BLOCKED:P1:selfable] [CLAIMED:5bfda407:2026-08-13T09:05] consolidate Step 2.4 PR create
```

| Piece | Value | Notes |
|-------|-------|-------|
| `[CLAIMED]` | literal | The lease tag |
| `<session>` | first 8 chars of the session id | Same source as `format.md`'s completion convention (`.ralph/.claude_session_id` in Ralph, else the current session id) |
| `<timestamp>` | ISO `YYYY-MM-DDTHH:mm` (24h) | The moment the claim was stamped or last refreshed — doubles as the lease clock for staleness |

**Not a hybrid marker.** `format.md` forbids `- [ ] [BLOCKED...]` because `[ ]` and `[BLOCKED]` are two mutually-exclusive *state* markers. `[CLAIMED:...]` is a *lease annotation*, not a state — so `- [ ] [CLAIMED:...]` and `- [BLOCKED:P*:selfable] [CLAIMED:...]` are both valid. The checkbox marker (`[ ]` / `[BLOCKED:...]`) is unchanged; the claim tag sits after it exactly like `[TRACKED]` / `[REVIEW_FEEDBACK]`.

Claim only `[ ]` and `[BLOCKED:P*:selfable]` items (both are workable-now). Never stamp a claim on `[x]` (already done) or `[BLOCKED:*:external]` (not progressable — nothing to claim).

## Lifecycle

### 1. Claim (before starting work) — HARD STOP: re-read first

Because the tracker is often under concurrent edit, **re-read the file from disk immediately before claiming** — an in-context snapshot may be stale.

1. Re-read the tracker; grep the target item for an existing `[CLAIMED` tag
2. If unclaimed (or the existing claim is stale — see "Stale claim & takeover") → add `[CLAIMED:<your-sid>:<now>]` after the checkbox marker
3. Save (and commit, in a git-tracked tracker) the claim edit **before** beginning the actual work, so concurrent readers see it promptly

### 2. Refresh (long-running work, optional)

For work spanning longer than the stale TTL, re-stamp `<timestamp>` to the current time periodically so a l

Github ReposUpdated 9h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.