wm
claudecodexWork lifecycle management v2 — phased workflows (research, plan, implement) with agents, commands, and hooks.
18 skills · 34 commands · 20 agents · hooks · LSP
Authoring aids for the Claude Code harness — skill shapes (workflow, loop, instruction, router), golden words that stand in for a rule set, pruning an existing skill or doc corpus into the house style, repo bootstrap (README, CLAUDE.md, deploy and adr skills, settings), and agent-work metrics from a per-turn ledger (re-ask ratio and causes, prompts to done, pasted blocks that should be a skill).
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin harness-dev in popoffvg/dotfiles. Commands read from the repo's manifest — 4 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
agent-metricsReport how the operator and the agent work together, from the per-turn ledger the harness-dev hooks write — re-ask ratio and its causes, prompts to done, prompt quality, pasted blocks that should be a skill, and "You should know" notes. Use for "agent metrics", "how are my prompts", "re-ask ratio",
help-commandUse when writing or fixing a `<router>:help` slash command in a plugin under harness/plugins/ — a command whose only job is to print a static help table/guide. Trigger on "add a help command", "write a help command", "the help command prints junk / shows load summary instead of the table", "fix code
prompt-dry-runUse when the user runs "/harness-dev:prompt-dry-run <prompt>" or asks to draft/preview/dry-run how a prompt would be handled — reflect back the agent's reading of the prompt (intent, planned actions, limits) BEFORE acting, so misalignment surfaces first. Trigger on "draft this", "what would you do w
prune-textRewrite a skill, an AGENTS.md/CLAUDE.md, or a doc corpus into the agent-writing house style — cut duplication across files, cut dead weight inside each file, then reshape into steps plus disclosed reference. Use when the user asks to prune, dedup, compress, or restyle docs or skills, or says files r
repo-settingsSet up a repository's base documentation and Claude configuration — README.md, CLAUDE.md, a per-repo deploy skill, a per-repo adr skill, and .claude/settings.json. Use for "set up this repo", "add repo settings", "bootstrap README and CLAUDE.md", "add a deploy skill to this repo", "set up ADRs here"
rule-conflictsFind contradicting and duplicate rules across the instruction corpus — global CLAUDE.md, loose and plugin skills, ~/.notes/rules. Triggers on "find contradictions in the rules", "which rules conflict", "check the corpus for duplicates", and after a session broke a rule that another rule seemed to al
session-cost-auditAudit why a Claude Code session was slow or expensive, and rank fixes onto existing harness levers. Triggers on "make sessions faster", "why did that session burn so many tokens", "where did the context go", "analyse this transcript", "too many turns per prompt", or any ask to profile a .jsonl under
text-styleShape agent-facing markdown into the house style — steps plus disclosed reference, a checkable completion criterion per step, leading words instead of restatements, positive targets instead of bans, and a description that fires as a context pointer. Load it when writing or rewriting a SKILL.md, an a
prune-blind-readerOver-cut detector for the `prune-text` skill — runs a pruned file as its only instruction, cold, and reports every point where it had to guess. Sees the pruned file and nothing else: no original, no cut list, no diff. Its guesses are the caller's over-cuts. Read-only on the corpus. Spawned once per
prune-mapperBounded read-and-report worker for the `prune-text` skill — reads a batch of files and emits one artifact: a topic map (phase 1) or an idea/property table (phase 2). Writes the artifact to a path and returns that path alone. Read-only on the corpus: it names what is there and never judges what to cu
python3 ${CLAUDE_PLUGIN_ROOT}/bin/turn-ledger.py
python3 ${CLAUDE_PLUGIN_ROOT}/bin/turn-ledger.py
Work lifecycle management v2 — phased workflows (research, plan, implement) with agents, commands, and hooks.
18 skills · 34 commands · 20 agents · hooks · LSP
Review comments on lines of any file, kept outside the file. Zed writes them through the line-comment language server; /line-comment:act reads the store and does the work, /line-comment:write places comments, /line-comment:unresolved reports what is still open, /line-comment:prune throws comments away, /line-comment:distill turns the habits act saved into review rules.
5 commands
Per-session prompt stack: push/pop/list/drop prompts across a session.
4 commands
Scores every Claude Code session for the lessons it holds and proposes where each one belongs in the harness: a watermarked background scan kicked by the SessionStart hook, one haiku call per dirty session, then a suggestion pass over the existing skill inventory. Browsable in the self-improve TUI. High scorers are archived for the capture-lesson skill to turn into skills and the dream skill to consolidate.
3 skills · hooks
Split the working tree of every nearby git repo into logical commits at hunk granularity. A sonnet subagent proposes the split into an editable file, the operator answers each block, a second subagent builds the commits in a throwaway worktree and cherry-picks them back.
1 skill · 1 command · 1 agent
Push, pop and list prompt drafts in files under ~/.claude/prompt-stack, from a key-opened menu
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.