Pipa deliver work
Operational skills for the agents people already use.
npx -y skills add lunchpaillola/pipa-skills --skill pipa-deliver-workAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants Pipa to coordinate active service delivery: status, blockers, risks, owners, handoffs, dependencies, triage, weekly client updates, QA, and next actions.
SKILL.md
1.5 KB, as published. Nobody here has run it
Pipa Deliver Work
Keep active client work moving.
When present, read ~/.pipa/profile.md once for durable business context. If missing, continue without blocking and do not start setup unless the user asks or a soft setup offer is useful.
Use For
- Status updates, weekly client updates, blockers, risks, escalations, and owner gaps.
- Delivery handoffs, dependencies, active client portal maintenance, QA, and triage.
- One-time updates and delivery coordination.
References
- Load
references/deliver-work.mdfirst. - Use
references/execute*.mdfor coordination, iteration, and handoffs. - Use
references/monitor*.mdfor status, triage, and risk. - Load
references/examples/deliver-work.mdwhen an example shape helps.
Output Contract
- Current state.
- Blockers, risks, or escalations.
- Owners, next actions, and due/review dates.
- Client/stakeholder update when useful.
- Evidence/source or
TBD.
Boundaries
- Recurring/event-driven delivery setup goes to
pipa-manage. - Money-impacting follow-up goes to
pipa-get-paid. - Relationship retention follow-up goes to
pipa-keep-clients.
Gotchas
- Do not imply work is done without acceptance evidence.
weeklycan mean reporting horizon, not automation.- Escalations and risk claims need evidence or
TBD.