dev-trackerlisted

# Dev Tracker A production-ready development journal for Claude Code that preserves project context across sessions without adding unnecessary process overhead. Use this skill for tracked software work where losing session context is costly. The skill keeps a clear boundary between: - raw user notes - chronological progress logs - permanent architectural decisions - living implementation conventions ## What this skill manages | File | Purpose | Ownership | |------|---------|-----------| | `TODO.md` | Raw notes, ideas, rough tasks, reminders | User-owned | | `DEVLOG.md` | Chronological session log: what happened, blockers, next steps | Claude-managed | | `DECISIONS.md` | Important decisions with rationale and revisit conditions | Claude-managed | | `CLAUDE.md` | Conventions, architecture notes, standards, recurring implementation facts | Skill-managed if skill-created; append-only if team-authored — see warning below | When a project uses Claude Code's native `memory/` store, the "Claude-managed" rows above defer to it — see "Coexistence with Claude Code auto-memory" below before treating `DEVLOG.md` / `DECISIONS.md` as the system of record. ### ⚠️ CLAUDE.md warning In Claude Code, `CLAUDE.md` is auto-loaded into the context of every session for that project. This means every byte written to `CLAUDE.md` is a byte of context tax paid on every future run. Keep `CLAUDE.md` lean. Only write durable, high-signal content: - architecture invariants that will not change for mo