spec-agent-memory

Files (1)

• SKILL.md

SKILL.md (first lines)

# Spec agent memory

Project-scoped memory lives in **`.agents/memory/`** (commit to git for team continuity). Cursor resolves the same content via `.cursor/agent-memory/` symlink.

## At session start

1. Read `.agents/memory/_project/MEMORY.md` (shared context). Cursor may inject a short summary — still open the file if you need full detail.
2. Read `.agents/memory/_project/specs-index.md` (REQ/ARCH/BUG status).
3. Read `.agents/memory/<agent-name>/MEMORY.md` for your role (e.g. `backend-engineer`). Create the file if missing (`# <role> memory` + `## Lessons`).

## What to record

- PRD/REQ features and implementation status
- Architecture decisions and component relationships (link ARCH/ADR paths)
- Codebase patterns, module locations, conventions
- Test patterns and common failure modes
- Phase/feature dependencies
- Useful technology notes from research (with links)
- Config and environment variable dependencies
- Blockers and known issues
- **Recipe** used (`bug-fix`, `maintenance`, etc.) and outcome

## File layout

| Path | Purpose |
|------|---------|
| `_project/MEMORY.md` | Shared — stack, conventions, links (keep ≤200 lines) |
| `_project/specs-index.md` | Table of REQ/ARCH/BUG status |
| `<agent-name>/MEMORY.md` | Role-specific durable notes |
| `<agent-name>/<topic>.md` | Deep dives; link from MEMORY.md |

## Guidelines

- Keep **`MEMORY.md` concise** — aim under **200 lines** (long files dilute attention).
- Use **topic files** (`debugging.md`, `patterns.md`, `infra.md`) for detail; link from MEMORY.md.
- Update or **delete** outdated memories.
- Organize by **topic**, not chronology.
- **Never store secrets**, tokens, or credentials.
- Prefer **paths and facts** over narrative; specs in `.specs/` remain source of truth — memory is an index, not a replacement.

## Learning journal (Cursor plugin hooks)

Cursor plugin hooks append to `_project/learning-journal.md` on spec/memory edits. **Distill** durable entries into `MEMORY.md`; delete noise from the journal periodically. Other tools: append manually or follow `SPECFORGE_HOME/MULTI-TOOL.md` checkpoint checklist.

## At session end

1. Update your agent `MEMORY.md` with new learnings.
2. Update `_project/specs-index.md` if spec status changed.
3. If a lesson applies to all agents, add one line to `_project/MEMORY.md`.
4. At **gate boundaries**, orchestrator writes checkpoint to `.specs/handoffs/`; do not rely on chat for next phase (Principle 8).

## HANDOFF addition

Add to HANDOFF when relevant:

```markdown
**Memory updated:**
- `.agents/memory/<agent>/MEMORY.md`
- [other files]
```

From sushilti80/specforge-engineering-team, MIT.

More from sushilti80/specforge-engineering-team