// Append a one-line learning to the local harny inbox. Fast, non-analytical capture — copies text verbatim, no analysis, no follow-ups. Use when the user wants to note something about harny adoption mid-conversation without breaking flow.
Onboarding and router for the harny plugin. Teaches the harny mental model (run anatomy, .harny/ state, architect role) and routes to focused skills. Use when adopting harny or unsure where to start.
Walk a repo through the harny readiness checklist. Score 10 dimensions Red/Yellow/Green, surface anti-signals, output a scorecard + prep checklist. Use when adopting harny in a new repo, or troubleshooting why it struggles in a familiar one.
Triage accumulated learnings from the local harny inbox into GitHub Issues, CLAUDE.md edits, or discards. Walks one entry at a time, verifies claims against current code, opens issues with provenance. Sister of /learn.
Orchestrate a release cycle across multiple harny runs. Dispatch with product-vision prompts, parallelize when safe, code-review every merge, triage findings into NOW-blocks/NOW-quick/BACKLOG. Use as release manager across N runs.
Post-mortem of a single harny run. Reads state.json + plan.json + per-phase transcripts. Emits a leaves-to-trunk review with evidence-backed proposals (triaged NOW-blocks/NOW-quick/BACKLOG). Use after failed, retried, slow, or novel runs.
| name | learn |
| description | Append a one-line learning to the local harny inbox. Fast, non-analytical capture — copies text verbatim, no analysis, no follow-ups. Use when the user wants to note something about harny adoption mid-conversation without breaking flow. |
| allowed-tools | Bash, Read, Write, Edit |
Fast, frictionless capture into the project's local harny inbox at <cwd>/.harny/LEARNINGS.local.md. Drained later by the drain skill.
The whole point is zero friction. The user is mid-conversation and wants to note something without breaking flow. Do not analyze. Do not ask follow-ups. Do not propose solutions. Capture and return.
Path: <cwd>/.harny/LEARNINGS.local.md. The cwd is the current working directory of the conversation.
If .harny/ does not exist, create it. The file .harny/.gitignore (containing * + !.gitignore) ships with harny runs and keeps everything inside .harny/ out of git, including this inbox. If .harny/ is being created here for the first time, also write that gitignore.
Use this header exactly:
# harny learnings inbox
Working memory, append-only, gitignored. Drain via `/drain`.
Entry format: `- [<ISO UTC timestamp> · <branch>] <text>`
2026-04-23T18:45:00Z. Use date -u +%Y-%m-%dT%H:%M:%SZ via Bash.git rev-parse --abbrev-ref HEAD. If the repo is detached or git errors, use -.Single-line format:
- [2026-04-23T18:45:00Z · main] the raw text verbatim
If the captured text has newlines, indent continuation lines with two spaces so the bullet list stays valid:
- [2026-04-23T18:45:00Z · main] first line
continuation
more continuation
Copy the user's text verbatim. Do not rewrite, do not summarize, do not "improve" the wording.
One short line back to the user, then return to whatever was being discussed:
Captured to
.harny/LEARNINGS.local.md. Back to what we were doing.
No questions. No analysis. No "would you like me to also...".
.harny/LEARNINGS.local.md and (on first creation) .harny/.gitignore.All of that belongs to the drain skill, invoked separately when the user is ready to triage accumulated entries.
args provided. Ask one short question: "What do you want me to capture?" — then return to the steps above. Do not ask for elaboration on the content.args starts with the word drain. Do not run capture. Tell the user this skill is for capture only and suggest /drain for triage. Do not invoke drain automatically..harny/ exists but is not a directory (e.g., a file with that name). Stop and report — do not overwrite.git command unavailable. Use - for the branch field rather than failing.