daily

Files (2)

• SKILL.md
• daily-state.py · scripts/

SKILL.md (first lines)

<!-- generated: third-party requirements -->
> **Requires:** `pip install pyyaml` — this skill's scripts import `yaml`.

# daily — the one command to remember

Route the user to the right skill for their moment in the day. You are a router:
ask at most two short questions, then hand off. Do not do the station's work
yourself — the destination skill owns it.

## Parse the argument first

`$ARGUMENTS` (if any) selects a station. Match case-insensitively against the
station words and synonyms:

| Station | Words |
|---|---|
| START | `start`, `morning`, `begin`, `plate` |
| WORK | `work`, `working`, `stuck`, `doing` |
| FILE | `file`, `filing`, `findings`, `tickets` |
| REPORT | `report`, `status`, `update` |
| WRAP | `wrap`, `done`, `end`, `finish`, `invoice` |
| SAVE | `save`, `pause`, `checkpoint` |

- **Match a station word** → jump straight to that station (no menu).
- **Match a SAVE word** → run the **Save state** flow (below). SAVE is NOT a
  numbered station and never shows the menu; it captures the resume-point and
  returns.
- **No argument, or no match** → show the menu. An unrecognized word is NEVER an
  error; show the menu with a one-line note ("didn't recognize '<word>'").

## Welcome back (read state, before the menu)

On **bare `/daily`** and on **`/daily start`**, BEFORE showing the menu or handing
off to START, read the saved work-state. Run from any cwd inside the project:

```bash
python "${CLAUDE_SKILL_DIR}/scripts/daily-state.py" show --json
```

- If the output is the literal text `no state yet` (a string, NOT JSON — it is
  printed under both plain and `--json` modes), **skip silently** and go straight
  to the menu / START. Never announce "no state."
- Otherwise `json.loads` the output and read `updated`, `station`, `status`,
  `focus`, and `next`. Compute the relative age yourself from `updated` (e.g.
  "2h ago") — it is NOT stored in the file. Then print one **welcome-back** line,
  the station in CAPS with its emoji, ticket if present:

  > *Last session (2h ago): 🔧 WORK on #6125 — cause confirmed. Suggested next → grill-then-plan.*

  Station emoji: ☀️ START · 🔧 WORK · 📋 FILE · 📣 REPORT · 🌙 WRAP.

Then continue: on bare `/daily` go to **Auto board** (below) before the menu; on
`/daily start` hand off to START. This is a read only — it never writes or commits.

## Auto board (bare `/daily`, after welcome-back)

On **bare `/daily`** only, after the welcome-back line (or after skipping it when
there is no state), **auto-render the work board as a supplement** before the menu —
so the user sees their resume-point AND their open work in one glance, without
picking a station. Invoke the **`my-work`** skill (`ado-backlog:my-work`; the
`github-backlog` twin `github-my-work` only if the project is GitHub-context or the
user asks).

- If the board cannot load (not logged in / offline / `ado-backlog` not installed),
  print a single line — *"board unavailable: <reason>"* — and continue. **A board
  failure must never block `/daily`**: the local log still shows. This is the
  local-first / board-as-a-component property — the resume-point is always available,
  even offline.

Then show the menu below. (`/daily start` already renders the board as its station,
so it is unchanged; this only adds the board to the bare, no-argument path.)

## The menu (bare /daily)

Present exactly five options and wait:

```
Where are you in your day?

  1. ☀️  Starting my day      — what's on my plate
  2. 🔧  Working / stuck      — route me to the right tool
  3. 📋  Filing findings      — turn findings into tickets
  4. 📣  Reporting status     — reshape work for leadership
  5. 🌙  Wrapping up          — daily summary from my commits

(Next time: /daily start · work · file · report · wrap)
💾 Save state anytime: /daily save "<note>"
```

The `Next time` line teaches the station shortcuts; the 💾 line teaches the save
accelerator — both graduate users from the menu. Save is a footer, not a sixth
option: the circle stays five stations (ADR 0004).

## Stations

### 1. START

First run the **Welcome back** read above (`daily-state.py show --json`) and, if
state exists, print the one-line welcome-back BEFORE the handoff — so the user sees
where they left off, then their board. Skip silently if there's no state.

Then invoke the **`my-work`** skill from the ado-backlog plugin
(`ado-backlog:my-work`). Mention the GitHub equivalent (`github-backlog`'s
`github-my-work`) ONLY if the user asks for GitHub.

### 2. WORK

Ask ONE question — "What's happening?" — with these options, then hand off:

| The user is… | Hand off to |
|---|---|
| designing something new | `grill-then-plan` |
| facing an effort too big for one session (foggy, multi-session) | `chart-map` (`/decision-map:chart`) to chart it; `work-map` (`/decision-map:work`) to continue a map already charted (maps live in `docs/decision-map/`) |
| dealing with something broken | `debug-mantra` — then follow the debug chain below |
| advising how a system should work | `study-design-verify` |
| auditing names / labels / mappings | `naming-audit` (or `fit-gap-analysis` for as-is vs to-be) |
| explaining a complex problem | `problem-description` |
| asking why code/a ticket exists | `ticket-trace` |
| wanting a second opinion | `scrutinize` (plans/local diffs) or `dual-verifier` (completed work) |

From ThodsaphonSonthiphin/workflow-daily-work, MIT.

More from ThodsaphonSonthiphin/workflow-daily-work