lunchpaillola/pipa-skills

pipa-daily-plan

Use only when `pipa-daily-plan` is explicitly invoked or `pipa-define-work` delegates to it.

First seen Aug 6, 2026

Installation

$ npx skills add lunchpaillola/pipa-skills --skill pipa-daily-plan

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lunchpaillola/pipa-skills · top by installs.

npx skills add lunchpaillola/pipa-skills

Browse all from lunchpaillola/pipa-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.1
More metadata
version
0.1.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,895 B
  • docs SUMMARY.md 115 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 70 installs

SKILL.md

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

  1. Read [references/gotchas.md](references/gotchas.md) and [references/output-contract.md](references/output-contract.md).
  2. 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.
  3. Read ~/.pipa/profile.md and ~/.pipa/CONNECTORS.md when present. Use the profile for goals and preferences. Use mapped tools when present. For unmapped capabilities, use composio-mcp discovery to find tools for project tracker, calendar, and ~~code hosting.
  4. Verify live access before reading a source. Use project tracker and calendar as core sources. Use ~~code hosting for code delivery. Use prior briefs, chat, email, or a knowledge base only to answer a specific planning question.
  5. Gather due work, current or active work, priorities, dependencies, calendar commitments, and stated goals or profile preferences.
  6. 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.
  7. 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.
  8. Write the read-only brief with [references/output-contract.md](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.