splisted

<purpose> Read the project's `status.md` (pm/status.md inside the pm [project management] folder in project root) and orchestrate session startup from cold context. Producer is `su` (status update); this skill is the consumer. Goal: understand current state, resume open work, and act on what's next without redoing work or asking questions the file already answers. </purpose> <rules> - Doubt = stop. If a task is unclear, contradictory, or a real decision is buried in it, ask before implementing - `status.md` = what's OPEN. Treat every item as live work, not history - `[files]` is your entry point, read the referenced files before editing - Respect `[decided]` (don't re-litigate) - Verify delegated or local work before marking it done. - Be concise in the startup summary, but don't skip important state. </rules> <inline_markers> - `[files]:` relevant paths, with line numbers when present - `[status]:` what's done, concrete next steps - `[decided]:` choices already made + why (don't re-open) - `[landmine]:` gotchas, deceptive code, don't-touch zones Markers are optional. Other markers may exist, interpret sensibly. </inline_markers> <workflow> 1. **Read `pm/status.md`.** If missing, say so and ask whether to create one (via `su`) or continue without it. 2. **Triage each item by judgment** (no category tags, decide from content): - Autonomous work Claude can own? Spawn subagent(s) aggressively, parallel when independent and non-colliding. Pass full context: `[files]`,