Plan Day

Render one plan for today from every enabled source in a My PA workspace. This skill plans; it never executes. Start ticket or bead work from the member workspace that owns it.

Requirements

• Run from a My PA workspace root, or below one: a directory holding both workspace.json and pa.toml. The helper searches upward and fails closed otherwise.
• Python 3.11+ runs scripts/plan_day.py; it is standard-library only.
• Collectors write their output under the workspace's ignored .artifacts/plan-day/. Sources whose collector is not yet implemented are reported as missing, never guessed.

Usage

/plan-day            # Plan today, carry over slippage from the previous plan
/plan-day --dry-run  # Render the plan without writing plans/YYYY-MM-DD.md or pruning

Reject unknown arguments before collecting.

Write boundary

The only files this skill writes are plans/YYYY-MM-DD.md in the workspace and collector output under .artifacts/plan-day/. Never create plan beads, never update Jira, Trello, Beads, Thoughtbox or Git, and never modify member repositories. Durable outcomes of planning go back to the owning source in a separate, user-confirmed interaction.

Collector contract

Every collector emits one JSON array of items with exactly these fields:

Validate before merging:

python3 ~/.agents/skills/plan-day/scripts/plan_day.py validate .artifacts/plan-day/*.json

Procedure

1. Config. python3 ~/.agents/skills/plan-day/scripts/plan_day.py config prints the validated pa.toml and the workspace root. Stop on any error; do not plan from defaults.

2. Collect. Run one collector per enabled source. Each validates its items and writes .artifacts/plan-day/<source>.json, printing a count and diagnostics. A source without a collector, or whose collector fails, stays in missing_sources and the plan says so.

   python3 ~/.agents/skills/plan-day/scripts/plan_day.py collect beads
   python3 ~/.agents/skills/plan-day/scripts/plan_day.py collect thoughtbox
   python3 ~/.agents/skills/plan-day/scripts/plan_day.py collect jira --client {name} --input .artifacts/plan-day/jira-{name}.raw.json

   • beads runs the /next helpers from the workspace root: ready candidates across every usable store plus in-progress claims per store, read-only. A bead is delegable when it is open, has both a description and acceptance criteria, and lacks the human label.
   • thoughtbox resolves a context for every [[clients]] and [[projects]] workspace and keeps Inbox thoughts only, at priority.thoughtbox_default. Members without a context are diagnostics, never failures; a missing thoughtbox CLI fails the whole source closed.

   • jira cannot be fetched from a script. For each [[clients]] entry with a jira table, query with the MCP tool and save the response verbatim as the --input file, then normalise:

     mcp__jira__jira_get
       path: /rest/api/3/search/jql
       queryParams:
         jql: assignee = currentUser() AND statusCategory != Done ORDER BY priority DESC, updated DESC
         fields: summary,status,priority,duedate
         maxResults: 50

     Priority names map through priority.jira; an unmapped name fails closed so the mapping is fixed in pa.toml rather than guessed. jira.base_url on the client builds the deep link. Never fetch with a JQL other than the one above and never write back to Jira.

3. Merge. python3 ~/.agents/skills/plan-day/scripts/plan_day.py merge validates every collector file, adds hours from the matching [[clients]] or [[projects]] entry, sorts by priority then due date, and lists missing and disabled sources.
4. Draft. python3 ~/.agents/skills/plan-day/scripts/plan_day.py draft merges, marks items present in the previous plan file as carried, proposes a block for each item, adds a paste-ready launch line, and writes .artifacts/plan-day/draft.json. Proposals: work hours go to work on a work day and skip otherwise; project-session hours go to project-session when delegable and evening when not; unmapped repositories go to evening; Jira items without a [[clients]] entry are skipped. In-progress and carried items sort first. The context says whether today is a work day and whether now is inside schedule.work_hours.
5. Judge. Read the draft and change only what the proposals get wrong: move an item between blocks, reorder within a block for a due date or a carried-over item, or set block to skip with a one-line reason when there is no capacity. Never invent items, edit titles, or change contract fields. Keep the number of work items to what fits schedule.work_hours and the number of project-session items to what can run concurrently unattended. Write the result back to .artifacts/plan-day/draft.json, or leave it untouched when the proposals stand.
6. Render. python3 ~/.agents/skills/plan-day/scripts/plan_day.py render --dry-run prints the plan; without --dry-run it writes today's file and deletes plans beyond plans.retention_days. Pass --decisions PATH when the judged file lives elsewhere. Show the rendered plan to the user; it is the deliverable.

Plan layout

The renderer owns this layout; do not hand-write plan files.

# Plan — {Weekday} {YYYY-MM-DD}

## Work
| # | Item | Source | Pri | Due | Status | Carried | Delegable | Launch |

## Project sessions
...

## Evening
...

## Skipped
- `{id}` {title} — {reason}

## Sources
missing: ...
disabled: ...

Launch is a paste-ready cl <path> or pl <path> line for the item's registered repository (launcher.command in pa.toml, default cl), so work starts there and not in this workspace. It is blank when the repository is unregistered.