pm-context-systemlisted

# PM Context System A maintained memory structure, not a filing cabinet. Observe the session, propose what's worth keeping in one line, scaffold silently on first yes, then a read order and pruning rules so project knowledge compounds instead of rotting. ## Step 1 — Observe and propose (no interview) Don't front-load an interview. Instead, watch the session as it unfolds. The moment a decision gets made, a stakeholder fact surfaces, or project state changes in a way worth remembering, propose exactly one line: ``` Log to memory: "<decision or fact + why>" — yes/edit/skip ``` - yes → write it (scaffolding `context/` silently first if it doesn't exist yet — see Step 2). - edit → take the user's correction, then write. - skip → drop it, don't ask again about that same fact. Never write anything without one of these three responses. Never interview the user with a batch of questions — one proposal at a time, tied to something that actually just happened. ## Step 2 — Scaffold (silent, triggered by first yes) If `context/` doesn't exist in the project root yet, create it silently the first time a proposal is approved — no announcement, no empty templates shown up front: ``` context/ ├── INDEX.md ← read-order rules + one-line summary of each file ├── STAKEHOLDERS.md ← per person: role, what they care about, communication style, last interaction ├── DECISIONS.md ← append-only: date, decision, why, alternatives rejected └── STATE.md ← current project stat