Pipa Define Work

Route fuzzy demand to one focused Define Work operation.

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.

Select One Operation

Explicit operation invocation wins. Otherwise select exactly one primary operation and preserve the user's business objective:

• pipa-problem-framing: clarify the problem, affected people, desired outcomes, success criteria, constraints, or non-goals.
• pipa-stakeholder-map: map stakeholders, RACI roles, decision authority, approvals, communication, or escalation paths.
• pipa-project-charter: assess charter readiness and make a go, go-with-conditions, or no-go viability decision.
• pipa-requirements-brief: turn notes or a broad project-planning ask into requirements, acceptance boundaries, and unresolved decisions.
• pipa-scope-baseline: baseline deliverables, exclusions, milestones, schedule assumptions, tolerances, and change triggers.
• pipa-roadmap: sequence candidate work into now/next/later or another requested prioritization method.
• pipa-decision-log: set up RAID, RACI, decision records, ownership, and review cadence.
• pipa-daily-plan: brief one specific workday around due work, active priorities, goals, and calendar commitments.