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.
- Confirm whether the need is risk/issue/dependency visibility, decision traceability, or review rhythm.
- Check stakeholder maps, roadmaps, scope baselines, assumptions, risks, dependencies, and pending decisions. Continue with incomplete data and mark gaps
TBD.
- Build a minimal RAID set of risks, assumptions, issues, and dependencies, each with owner, next action, and review date or
TBD.
- 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.
- Create decision records with statement, options, owner, due/review date, status, evidence, and a practical review cadence.
Output Contract
# RAID RACI Decision Setup - <project name or YYYY-MM-DD>
## Objective
- Governance objective:
## Tool Access Check
- Tools and systems used:
- Data sources used:
- Missing tools or data gaps:
## Current Signal
- Governance readiness level:
- Most urgent control gap:
## RAID Snapshot
| Item | Type (`risk`\|`assumption`\|`issue`\|`dependency`) | Owner | Next action | Due/review date | Status |
|---|---|---|---|---|---|
## RACI Matrix
| Decision/control point | Responsible | Accountable | Consulted | Informed | Evidence/source |
|---|---|---|---|---|---|
## Decision Log
| Decision | Options | Owner | Due/review date | Status | Evidence/source |
|---|---|---|---|---|---|
## Actions
| Item | Owner | Next action | Due/review date | Status | Evidence/source |
|---|---|---|---|---|---|
## Unknowns
- TBD:
## Follow-ups
- Control artifacts to finalize before execution:
- Recommended next skill: `pipa-work-coordination`
Safety
- Never hide owner/date gaps or assign authority without evidence.
- Keep governance lightweight and operational.
- Read-only discovery and analysis do not require approval and must not be blocked on write permission; immediately before every external or file write, request separate explicit approval scoped to that exact action, destination, and proposed content, never treating the original request or approval for another write as approval; after each approved write, report success or failure and include the resulting path, link, or stable ID when available.
1---2name: pipa-decision-log3description: Use only when `pipa-decision-log` is explicitly invoked or `pipa-define-work` delegates to it. Do not trigger from generic language.4---56# Pipa Decision Log78Establish lightweight RAID and decision controls.910Apply `~/.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.1112## Workflow1314Track governance objective, source check, RAID set, RACI map, decision log/cadence, and final handoff in working notes as each step completes.15161. Confirm whether the need is risk/issue/dependency visibility, decision traceability, or review rhythm.172. Check stakeholder maps, roadmaps, scope baselines, assumptions, risks, dependencies, and pending decisions. Continue with incomplete data and mark gaps `TBD`.183. Build a minimal RAID set of risks, assumptions, issues, and dependencies, each with owner, next action, and review date or `TBD`.194. 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.205. Create decision records with statement, options, owner, due/review date, status, evidence, and a practical review cadence.2122## Output Contract2324```md25# RAID RACI Decision Setup - <project name or YYYY-MM-DD>2627## Objective28- Governance objective:2930## Tool Access Check31- Tools and systems used:32- Data sources used:33- Missing tools or data gaps:3435## Current Signal36- Governance readiness level:37- Most urgent control gap:3839## RAID Snapshot40| Item | Type (`risk`\|`assumption`\|`issue`\|`dependency`) | Owner | Next action | Due/review date | Status |41|---|---|---|---|---|---|4243## RACI Matrix44| Decision/control point | Responsible | Accountable | Consulted | Informed | Evidence/source |45|---|---|---|---|---|---|4647## Decision Log48| Decision | Options | Owner | Due/review date | Status | Evidence/source |49|---|---|---|---|---|---|5051## Actions52| Item | Owner | Next action | Due/review date | Status | Evidence/source |53|---|---|---|---|---|---|5455## Unknowns56- TBD:5758## Follow-ups59- Control artifacts to finalize before execution:60- Recommended next skill: `pipa-work-coordination`61```6263## Safety6465- Never hide owner/date gaps or assign authority without evidence.66- Keep governance lightweight and operational.67- Read-only discovery and analysis do not require approval and must not be blocked on write permission; immediately before every external or file write, request separate explicit approval scoped to that exact action, destination, and proposed content, never treating the original request or approval for another write as approval; after each approved write, report success or failure and include the resulting path, link, or stable ID when available.
lunchpaillola