Install
$ agentstack add skill-lunchpaillola-pipa-skills-pipa-define-work ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Pipa Define Work
Turn fuzzy demand into work that can be delivered.
Use For
- Scope, requirements, proposals, briefs, plans, charters, and decision records.
- Client/project onboarding after work is won.
- Client portal setup when it defines how an engagement will run.
- Acceptance checks, out-of-scope boundaries, owners, dates, and source gaps.
References
- Load
references/define-work.mdfirst. - Use
references/initiate*.mdfor context, stakeholders, problem framing, and viability. - Use
references/plan*.mdfor requirements, scope, roadmap, RAID/RACI, and decisions. - Load
references/examples/define-work.mdwhen an example shape helps.
Output Contract
- Working brief.
- In scope and out of scope.
- Acceptance checks.
- Decisions made and decisions needed.
- Owners, dates, and next actions.
- Source/evidence or
TBD.
Boundaries
- Pipa onboarding, business profile, preferences, connectors, and company brain setup go to
pipa-manage. - Active delivery updates go to
pipa-deliver-work.
Gotchas
- Use
TBDfor missing owners, dates, source facts, acceptance checks, or decisions. - Do not turn fuzzy context into committed scope without identifying assumptions.
- External docs, project records, or client-facing artifacts require approval before writes.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lunchpaillola
- Source: lunchpaillola/pipa-skills
- License: MIT
- Homepage: https://usepipa.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.