Menu
Use the local agent workspace memory model. Store durable hot memory in the agent `memory/` folder, use `notes/` for daily records and task-local notes, and keep both folders updated as work progresses.
| name | memory-use |
| description | Use the local agent workspace memory model. Store durable hot memory in the agent `memory/` folder, use `notes/` for daily records and task-local notes, and keep both folders updated as work progresses. |
Use this skill when the task involves saving, updating, or organizing agent-local memory.
This skill is for the TeamClaw agent workspace layout:
$HOME/<company-name>/agents/<agent-folder>/memory$HOME/<company-name>/agents/<agent-folder>/notesUse the two folders differently:
memory/ is for durable hot memory that should persist across ticketsnotes/ is for daily records, working notes, temporary checklists, and task-level scratch filesDo not mix long-term memory and day-by-day notes into the same file.
Use this skill for requests like:
memory/.notes/.Put these in memory/:
Put these in notes/:
memory/notes/Technical guide for creating a new TeamClaw agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new local coding agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Use a file-only git working branch for agent changes. Start from the current main branch contents without carrying prior branch history, create a fresh branch named from the agent or a uuid, then make the code update there.
Hire an Engineer in TeamClaw. Use this when an Architect or Manager needs to add implementation capacity, choose the right engineer role fit, check headcount, and then execute the hire through the standard TeamClaw agent creation flow.
Use the local deterministic infra layer in `tools/infra/` when setting up or extending harness, testbed, or local server environment workflows. Read the infra README first, then wire the setup into `Makefile` where appropriate.
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable TeamClaw release changelog at releases/v{version}.md by reading commits, changesets, and merged PR context since the last stable tag.