lunchpaillola Pipa Daily Plan
Create a brief for one workday. Route recurring or scheduled setup to pipa-manage.
Follow this workflow. Keep a todo list to track each step.
Workflow
- Read references/gotchas.md and references/output-contract.md.
- Use the system date for today. For another date, use the user's request or calendar. Ask one question only if the target day is unclear.
- Read
~/.pipa/profile.mdand~/.pipa/CONNECTORS.mdwhen present. Use the profile for goals and preferences. Use mapped tools when present. For unmapped capabilities, usecomposio-mcpdiscovery to find tools for~~project tracker,~~calendar, and~~code hosting. - Verify live access before reading a source. Use
~~project trackerand~~calendaras core sources. Use~~code hostingfor code delivery. Use prior briefs, chat, email, or a knowledge base only to answer a specific planning question. - Gather due work, current or active work, priorities, dependencies, calendar commitments, and stated goals or profile preferences.
- Find work the user can advance today. If due work is blocked, select an unblock step. If none exists, flag the block and continue to executable work.
- Choose the main focus in this order: overdue or due-today work, current or active work, then the best ticket that supports the user's goals or preferences. Do not estimate task size or forecast capacity.
- Write the read-only brief with references/output-contract.md. Show each exact external write and require separate approval before execution; report its result. End with a short sources line that names only the apps and material records used.