decision-ledger-hygiene

name	decision-ledger-hygiene
description	Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.
when_to_use	Session end, major trade-off, cross-org handoff, blocker resolution, superseding a prior decision.

Decision ledger hygiene

Role

Mike (Engineering Orchestrator) is accountable for Engineering decision continuity (per protocols/memory_and_logging_protocol_v1.md). Former single-agent / steward playbooks are archived; this skill is the procedure layer.

Pair with

• session-notes — Engineering session log in [PRODUCT_CODE_ROOT]/docs/agent_method/
• shared_context/ — cross_org_decisions.md, project_status_sync.md for XD and cross-org items

Load

• Pack note: Prior deep playbooks are not shipped here; use current org_engineering/agents/ specs + this skill.

Checklist

1. Material decision → log with ID, certainty tag, refs, next action
2. Supersession — never silent; link old → new entry
3. Handoffs — YAML/schema per hq_handoff_schema_v1.md when HQ ↔ Engineering
4. Open blockers — visible in session notes or sync files
5. Orchestration — assign clear next owner (specialist vs Orchestrator per task)

Stop conditions

• Do not close a session with orphan decisions (nothing written)

Cursor

Subagents do not own the ledger; Mike (Engineering Orchestrator) writes or approves log entries.