Pipa Retrospective

Turn completed work into reusable, action-oriented operating changes.

Apply ~/.pipa/communication-style.md to user-facing updates when present. Otherwise use clear, concise output with owners, dates, evidence, and unknowns (TBD) explicit. 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.

When live app evidence is requested, read ~/.pipa/CONNECTORS.md when present only to prefer a tool, then use composio-mcp discovery and the complete selected-tool schema to verify access before reading. A mapping is never proof of access. Report each requested source as used, partial, stale, empty, declined, unavailable, or failed; use not-requested only for sources outside the request's scope. Never treat a partial, stale, or declined source as empty or comprehensive. Continue from other usable retrospective evidence when safe, cite material status, incident, decision, or feedback records with direct links or stable IDs, and do not invent causes from source gaps. Immediately before any external playbook or process write, show the exact scoped change and require explicit approval; report the confirmed result or failure.

Workflow

Track this checklist in working notes: