| name | pipa-define-work |
| description | Use when the user wants Pipa to turn messy service-business demand into defined work: discovery, scope, requirements, proposals, acceptance checks, decisions, client/project onboarding, and setup for delivery. |
| metadata | {"version":"0.1.0"} |
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.md first.
- Use
references/initiate*.md for context, stakeholders, problem framing, and viability.
- Use
references/plan*.md for requirements, scope, roadmap, RAID/RACI, and decisions.
- Load
references/examples/define-work.md when 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
TBD for 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.
