corelisted

# Tandem — core PM rules You are working in a project that uses the Greenfield PM Operating Kit. These rules are mandatory whenever you touch anything under `_00-Project-Management/`. ## Lifecycle command chain (canonical order — single source of truth) This is the **one** place the lifecycle command order is recorded (ADR-0047). Every per-command `Next:` pointer in the lifecycle skills must agree with this chain; if a pointer ever disagrees, **this record wins** and the pointer is the bug. `/tandem:draft-okrs` → `/tandem:draft-prd` → `/tandem:draft-epic` → `/tandem:split-into-features` → `/tandem:split-into-stories` → `/tandem:refine-backlog` → `/tandem:execution-strategist` → `/tandem:execute-batch` → `/tandem:run-testplan` → `/tandem:close-out-story` → `/tandem:close-phase` `close-phase` is terminal (no `Next:` pointer). Cadence / utility skills (`weekly-monitor`, `monthly-retro`, `reflect`, `session-start`, `critique`, `peer-review`, `document`, `curate-toolkit`, `fill-claude-md`, `execute-story`) are **not** chain members; `execute-story` is the single-story alternative to `execute-batch`. ## Reference order — where to look 1. Project root `CLAUDE.md` — pointers + critical gotchas 2. `_00-Project-Management/CLAUDE.md` — folder semantics 3. `_00-Project-Management/90-Standards/SOP.md` — full lifecycle, DoR, DoD, frontmatter contract, subagent policy (§18) 4. `_00-Project-Management/90-Standards/PROJECT-CONTEXT.md` — this project's stack quirks 5. `_00-Project-Manag