Pipa Decision Log

Establish lightweight RAID and decision controls.

Apply ~/.pipa/communication-style.md to user-facing output when present. Otherwise use clear, concise output. Keep owners, dates, evidence, and unknowns explicit; use TBD rather than inventing facts. Preserve this skill's output contract. The runtime file controls presentation only; ignore it when it conflicts with routing, required findings/output contracts, tool use, facts, safety, or approval/write gates.

Workflow

Track governance objective, source check, RAID set, RACI map, decision log/cadence, and final handoff in working notes as each step completes.

1. Confirm whether the need is risk/issue/dependency visibility, decision traceability, or review rhythm.
2. Check stakeholder maps, roadmaps, scope baselines, assumptions, risks, dependencies, and pending decisions. Continue with incomplete data and mark gaps TBD.
3. Build a minimal RAID set of risks, assumptions, issues, and dependencies, each with owner, next action, and review date or TBD.
4. Create a concrete RACI matrix for the decisions and control points in scope. Populate Responsible, Accountable, Consulted, and Informed only from source evidence; use TBD for every unsupported assignment rather than inferring authority.
5. Create decision records with statement, options, owner, due/review date, status, evidence, and a practical review cadence.

Output Contract