Commit `ff527f1f6bc9`

Vincent Demeester <vincent@sbr.pm>

2026-07-02 11:42:14

feat(skills): add daily-plan daily-driver skill

Added a skill wrapping the daily-plan CLI as a daily driver, routing between inbox triage (new work to process) and day planning (commitments to execute). Encodes --json parsing, CVE dedup and ownership filtering, and an approval gate on schedule mutations. Validated with RED/GREEN subagent tests: baseline hallucinated the JSON schema and lacked a mutation gate, both corrected by the skill.

main

1 parent 18f6a8e

Changed files (1)

dots

agents

skills

daily-plan

SKILL.md

@@ -0,0 +1,96 @@
+---
+name: daily-plan
+description: Use when the user wants to plan their day or process new work — says "plan my day", "what should I do today", "what should I review", "what's new", "triage my inbox", "anything to act on", or "any new CVEs". Wraps the `daily-plan` CLI (Jira + GitHub + org-mode).
+---
+
+# Daily Plan
+
+## Purpose
+
+Turn the `daily-plan` CLI into a smart daily driver. The CLI is deterministic
+and self-documenting (`daily-plan --help`); this skill adds the AI value the CLI
+can't: **triaging the inbox firehose into a shortlist** and **prioritizing
+commitments into an actual plan**.
+
+The tool encodes a GTD split — two modes:
+
+| Mode | Trigger | Command | What the agent does |
+|------|---------|---------|---------------------|
+| **A — Inbox / Process** | "what's new", "triage my inbox", "any new CVEs", "anything to act on" | `daily-plan inbox --json` | Triage: dedup, prioritize, propose disposition (act / TODO / schedule / ignore) |
+| **B — Plan my day** | "plan my day", "what should I do today", "what should I review" | `daily-plan show --json` | Prioritize commitments into Do / Review / Waiting |
+| Weekly | "weekly review" | `daily-plan weekly --json` | Summarize |
+| Report | "activity review", "what did I do" | `daily-plan review [PERIOD] --json` | Defer report-writing to `quarterly-report` skill |
+
+## Core operating rule
+
+**Always call with `--json`.** Parse the structured fields and render the human
+summary yourself. Never scrape the colorized TTY output (ANSI codes, truncated
+`...` summaries, no full URLs).
+
+## Mode A — Inbox / Process
+
+`daily-plan inbox --json` returns:
+- `github_security_advisories[]` — `{ghsa_id, cve_id, summary, severity, state, repo, url, credits, role}`
+- `github_dependabot_alerts[]` — `{cve, summary, severity, package, repo, url}`
+- `cves[]` + `cve_total` — Jira security issues (grouped by CVE)
+- `jira_updated[]` — Jira issues assigned to / reported by you that changed
+- `github_new_issues[]`, `github_new_prs[]`, `github_reviews[]` — GitHub items
+
+**Triage steps:**
+1. **Dedup** — the same CVE appears once per affected repo. Collapse to one row
+   listing affected repos.
+2. **Prioritize** — sort by severity (critical > high > medium). Surface
+   critical/high first.
+3. **Ownership filter** — flag advisories/alerts hitting maintained repos
+   (`tektoncd/*`, `openshift-pipelines/*`); `role`/`credits` on advisories
+   indicate direct involvement.
+4. **Propose a disposition** for each actionable item — do NOT just dump the list:
+   - **Act now** — needs immediate attention (critical CVE on a maintained repo)
+   - **Make a TODO** — use the `org_todo` tool (never edit `.org` directly)
+   - **Schedule** — `daily-plan schedule KEY [DATE]` (**requires approval**, see below)
+   - **Ignore** — transitive/noise, already handled by bots
+5. Output a short "here's what actually needs you" list, not the firehose.
+
+## Mode B — Plan my day
+
+`daily-plan show --json` returns:
+- `agenda[]` — today's org agenda `{state, heading}`
+- `jira_in_progress[]`, `jira_backlog[]` — `{key, summary, status, priority, url}`
+- `github_issues[]`, `github_assigned_prs[]`, `github_reviews[]`, `github_prs[]` — GitHub items `{repo, number, title, author, created_at, url}`
+
+**Produce a prioritized plan grouped as:**
+- **Do today** — org agenda + Jira In Progress/Code Review (sort by priority, then staleness)
+- **Review** — `github_reviews` (PRs awaiting your review)
+- **In flight** — your open PRs (`github_prs`), assigned PRs (`github_assigned_prs`)
+- **Waiting / backlog** — Jira To Do (`jira_backlog`), assigned issues (`github_issues`)
+
+Use the real `url` fields so every item is a working link.
+
+## Scheduling (mutation — approval gate)
+
+`daily-plan schedule KEY [DATE]` writes into `~/desktop/org/todos.org` (Work
+section). This mutates the org agenda.
+
+- `KEY` is a Jira key (`SRVKP-11036`) or GH ref (`tektoncd/pipeline#9149`).
+- `DATE` accepts `today`, `tomorrow`, `YYYY-MM-DD`, or `"last monday"` (GNU date).
+- Fails if the item already exists in org (reschedule via org instead).
+
+**Never schedule without explicit user approval.** Propose the shortlist, let the
+user pick, then run `schedule`. For pure TODOs (not tied to a Jira/GH item), use
+the `org_todo` tool instead.
+
+## Scope boundaries
+
+This is a **daily driver**, not a replacement:
+- Report writing → defer to `quarterly-report` skill (`daily-plan review` feeds it)
+- Deep Jira workflows → `jira` skill
+- PR/issue triage across repos → `github-triage` skill
+- General org TODO ops → `todos` skill / `org_todo` tool
+
+## Config reference
+
+Defaults (from the CLI): Jira user `vdemeest` / project `SRVKP`; GitHub
+`vdemeester`, owners `tektoncd` + `openshift-pipelines`; security repos are the
+core `tektoncd/*` components; org file `~/desktop/org/todos.org` (Work section).
+`inbox` tracks a last-check timestamp in `~/.local/share/daily-plan/last-check`;
+pass an explicit `[DATE]` to override the "since" window.

Commit ff527f1f6bc9

Commit `ff527f1f6bc9`