agent-memory

Files (1)

• SKILL.md

SKILL.md (first lines)

# Agent memory

Feedback is wasted if the next session repeats the same miss. Prefer the **harness** over hand-editing.

## Structured path (preferred)

1. On self-review, put durable misses in `verdict.json` as `metadata[]` (reviewer may only flag; parent may fill):

```json
{
  "verdict": "good",
  "summary": "one sentence",
  "risks": [],
  "metadata": [
    {
      "target": "agents",
      "text": "Isolation default is native git worktree; treehouse is opt-in.",
      "reason": "review assumed treehouse"
    },
    {
      "target": "rule",
      "path": ".claude/rules/python-tests.md",
      "globs": ["**/*.py"],
      "text": "Prefer pytest for new packages.",
      "reason": "PR comment"
    }
  ]
}
```

2. Conductor auto-applies when `agent_memory.auto_apply: true` (default), writing `memory-applied.json` in the run dir.
3. Manual: `python3 ~/.claude/hooks/dev-loop/cli.py agent-memory --repo REPO --verdict PATH` (or `--key TICKET`).

Targets: `agents` | `rule` | `context` | `readme`. Rules must be path-scoped (`globs`, never `always_apply`). Secrets/hooks paths are rejected. `durable: false` is rejected.

## When (still apply by hand if no verdict)

- User/PR review corrects how agents should work and you are not going through `verdict.json`.
- A domain term or hard-to-reverse decision was resolved (`domain-glossary`).

Skip: one-ticket AC, style nits, speculative rewrites, secrets, SessionStart text.

## Where (pick one)

| Signal | File | Rule |
| ------ | ---- | ---- |
| Convention every future agent on **this repo** must keep | `AGENTS.md` / `CLAUDE.md` | Harness appends under `## Agent memory`. |
| Stack law missing for a path | path-scoped `.claude/rules` / `.cursor/rules` | `alwaysApply: false` + `globs`. |
| Domain term | `CONTEXT.md` via `domain-glossary` | Glossary only. |
| Hard to reverse + surprising + real trade-off | `docs/adr/` via `domain-glossary` | Skip unless all three. |
| Install / usage / public API would be wrong | `README.md` | That case only. |

Reviewer is read-only on metadata files. Parent writes `metadata[]` or calls the CLI.

## Do not

- Invent ADRs or always-on rules.
- Stow notes into SessionStart or CLAUDE.md tax.
- Update conductor secrets, hooks, or `~/.config/dev-conductor/secrets.env`.
- Copy skill bodies into AGENTS.md.
- Treat `SPEC_APPROVED` as ticket-done or chat as the source of Jira AC.

From sardul3/dev-conductor, MIT.

More from sardul3/dev-conductor