# Start Session (PM/Planning Agent)

Begin a work session — check active work, stale issues, and present a status dashboard.

Read `.claude/skills/flydocs-workflow/session.md` and follow the session start procedure.
Read `.claude/skills/flydocs-workflow/reference/script-catalog.md` for script calling conventions.

Triggers: "start session", "what's going on", "pick up where I left off"

$ARGUMENTS

## Opening on the right work (FLY-1098)

Lead with a focused read — `issue_list` with `focused: true`, or
`flydocs run issue.list --focused`. It resolves to the active sprint or board, so it is
the shortlist the developer actually has in flight.

- Report out-of-focus assigned work as a **count**, not an enumeration.
- If the note says focus could not be resolved, say so plainly — it means the workspace
  has no active sprint or the config is stale (`flydocs update` refreshes it). Do not
  silently fall back to listing everything.
- Wider listings (`--mine`, `--project`, `--all`) remain available on request.