← ClaudeAtlas

crew-contextlisted

How crew holds project state across sessions — the .planning state model and what each file owns. Use when reading/writing .planning state or resuming work.
mantaray0/crew · ★ 1 · AI & Automation · score 77
Install: claude install-skill mantaray0/crew
# crew Context & State ## The `.planning/` files (committed) | File | Owns | |---|---| | `PROJECT.md` | The living project truth: architecture decisions (the *why*), current state, constraints, a **stack table mirrored from `config.stack`** (the source of truth), plus an optional `## Reference` index. Loaded automatically at session start. | | `ROADMAP.md` | The fahrplan: milestones → phases with status markers + timestamps. | | `plans/<n>_<milestone-slug>/` | Detail per milestone (folder prefixed with the milestone number so it sorts & reads at a glance when collapsed): `_spec.md` (present for brief-driven milestones, then **permanent** — the milestone Spec, single source of intent) + numbered `<id>_<title>.md` phase plans (Scope note + `_spec.md` reference + Plan body each). | | `BACKLOG.md` | Idea inbox; triaged at plan/adjust. | | `LOG.md` | Append-only history: phase, commit, verify result, token/cost. | | `claims.json` | Which instance/worktree holds which phase (parallel-safe). | | `config.json` | Behavior config: cross-cutting top-level (`git`, `models`, `tasks`, …) + the workflow steps under `config.workflow.*` (`brief`/`plan`/`execute`(+`verify`)/`ship`/`learn`/`complete`/`finish`). | | `archive/` | Completed milestones moved out of live state (`/crew:archive`): `plans/<n>_<slug>/` with the former ROADMAP section written in as `_roadmap.md`. Keeps `ROADMAP.md`/`plans/` small. | | `reference/` | Load-on-demand knowledge docs (runbooks, domain/data maps, architectur