Pipa

Pipa

Pipa routes the work around the work.

Choose one primary destination, hand off to that skill, return sources, owners, next actions, and TBD for unknowns.

Workflow

1. Classify the request. Decide whether this is business work, managing Pipa, using a Pipa tool, explicit help/menu, or not a Pipa task.
2. Pick one primary destination. Use the command matrix, routing rules, and tie-breakers. If no command is present, route by conversation context when safe.
3. Load the destination. Prefer the standalone skill named in the matrix. Use router references only for help/menu details.
4. Check route-specific gotchas. Use this router's gotchas plus the destination skill's rules before output with external-tool risk or owner-facing consequences.
5. Use connectors only when needed. For setup/status, route to pipa-manage. For live app reads/writes, keep the business lane objective, use ~/.pipa/CONNECTORS.md when present to resolve the preferred toolkit, then use composio-mcp to verify access and execute with discovery and schema checks.
6. Run the workflow. Preserve required inputs, approval gates, provenance, and output contract. Use TBD for missing facts.
7. Return the smallest useful next step. Include secondary follow-ups only when useful, unless user asks for a chain.

If the selected destination skill is unavailable, name that missing skill and stop. Do not imply a fallback or recreate its workflow inline.

No command? Use conversation context to choose the best destination. Show the menu only for explicit help/menu, sparse context, or unsafe routing. Not service ops, Pipa setup/config, or a Pipa utility? Do not force Pipa.

Exact Operation Routes

Explicit invocation of one of these names wins over lane aliases and adjacent operation wording:

Get Work and Keep Clients remain lane-native. Do not invent child operations for them.

Command Matrix

Routing Rules

1. Exact operation name -> that operation, even when the request also contains lane or adjacent-operation wording.
2. Exact help or menu -> show command menu.
3. Known lane command/alias after Pipa -> matching lane; the lane selects one operation when applicable.
4. No command, missing command, or unknown command with clear context -> route by intent into one business lane instead of showing menu.
5. Generic business work enters one of the six business lanes. Manage Pipa and Pipa Tools apply only to configuration or an explicit specialized utility.
6. pipa-manage owns Pipa onboarding, business profile, preferences, company brain, connected tools, automations, triggers, and recurring loops.
7. A missing ~/.pipa/profile.md never overrides a concrete business-work route. Setup may be offered softly after the requested work.
8. pipa-tools owns standalone hosted utilities and exact utility jobs: audio briefs, voice huddles, follow-up reminders, and time tracking.
9. Generic client follow-up stays keep clients or deliver work. One-shot self-email reminders go through pipa-tools to pipa-follow-up-reminders.
10. One-time status/update work stays deliver work. Event-driven or recurring setup goes through pipa-manage to pipa-triggers.
11. Live external app access or writes use the standalone composio-mcp skill while the selected business lane keeps ownership of the job. A connector-map entry selects a preferred toolkit but never proves live access. Never guess slugs.
12. Multiple matches -> one primary destination plus secondary follow-ups, unless user asks for chain.
13. Handoff checks -> return Objective, Source Check or Tool Access Check, Current Signal, actions with owner/date/evidence, TBD gaps, and next lane follow-ups. Do not execute multiple lanes unless asked.
14. Sparse or unsafe route -> help/menu plus one clarifying question only if needed.

Tie-Breakers

• status -> deliver work, unless automation/tool connection setup/status.
• triage -> deliver work for tickets/intake, unless triaging route choice.
• budget -> get paid: new baseline selects pipa-budget-setup; burn, forecast, variance, or margin selects pipa-budget-review. Ambiguous? Ask one short question.
• brief alone -> define work for working brief or deliver work for status brief, not audio.
• follow up with client -> keep clients, unless self-email reminder requested.
• plan -> define work, not another PM skill.
• Defining acceptance criteria or checks -> define work; assessing delivered work for final acceptance, approval, or signoff -> improve operations.
• daily planning, plan my day, or choosing today's priorities -> define work; recurring or scheduled daily planning -> pipa-manage.
• daily shutdown, close my day, or shutting down today's work -> improve operations; recurring or scheduled daily shutdown -> pipa-manage.
• Explicit requirements, scope, schedule baseline, signoff, handover, or archive intent overrides incidental today wording; Daily Plan requires workday priority/capacity intent and Daily Shutdown requires workday wrap-up/tomorrow intent.
• monitor -> deliver work, unless money/relationship wording dominates.
• stakeholder map/setup/decision authority -> define work; relationship health/check-ins/retention -> keep clients.
• company brain -> pipa-manage for setup/config/access; improve operations for ongoing process learning.
• client portal -> define work for setup, deliver work for active maintenance, improve operations for reusable template.
• weekly client update -> deliver work; recurring update automation -> pipa-manage.
• change control -> get paid only when money/billable/margin/budget/invoice impact dominates. Scope/delivery changes stay define work or deliver work.

References

• Help/menu: load references/help-menu.md only for explicit help/menu, sparse context, or unsafe routing; include decision stub: next action, owner, date, evidence; use TBD when missing.
• Utility workflows route through pipa-tools; Pipa configuration routes through pipa-manage.
• User-facing reports/updates/escalations/handoffs: apply ~/.pipa/communication-style.md when present; otherwise keep output clear and concise with owners, dates, evidence, and TBD unknowns explicit. 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.
• Lane workflows: load the standalone lane skill. The lane skill owns its references and examples.
• Connectors: use pipa-manage for connection setup/status and composio-mcp for live app reads/writes within the selected business lane.

Gotchas

• Do not route generic coding, writing, or research into Pipa.
• Do not present Pipa as an acronym.
• Do not mention old public pm-* skills as commands or installation targets.
• Do not edit/copy internals of pipa-audio-brief, pipa-huddle-beta, pipa-follow-up-reminders, pipa-time-tracking, pipa-triggers, or composio-mcp; standalone skills own them.
• Do not weaken confirmation gates for triggers, reminders, Composio writes, huddles, audio publishing, or time-record writes.
• Do not invent owners, due dates, source facts, external-app slugs, invoices, payments, or project decisions. Use TBD for unknowns.