/start

name: sc:start
description: Warm-start session briefing — displays GSD position, recent activity, pending suggestions, and skill budget
allowed-tools:
  - Read
  - Bash
  - Glob

/sc:start — Warm-Start Session Briefing

<objective> Orient the current Claude session with a warm-start briefing that displays:

1. **GSD Position** (SESS-01) — Current phase/plan position from STATE.md 2. **Recent Activity** (SESS-02) — Latest session observations from sessions.jsonl 3. **Pending Suggestions** (SESS-03) — Unreviewed skill suggestions with occurrence counts 4. **Skill Budget** (SESS-04) — Active skills and token budget usage

Run this command at the start of every session for full context awareness. </objective>

<process>

Step 0: Read Integration Config

Read `.planning/skill-creator.json` using the Read tool.

• If the file does not exist, proceed with all features enabled (opt-out model: everything defaults to `true`).
• Parse the JSON to extract:
• `integration.suggest_on_session_start` (controls SESS-03)
• `token_budget.max_percent` and `token_budget.warn_at_percent` (used in SESS-04)
• If parsing fails or the file is empty, proceed with defaults:
• `suggest_on_session_start`: true
• `max_percent`: 5
• `warn_at_percent`: 4

Store these values for use in later steps.

---

Step 1: Run Monitoring Scan (MON-03)

If `integration.phase_transition_hooks` is `true` (from Step 0 config), run a passive monitoring scan to detect changes since the last session.

Read `.planning/patterns/scan-state.json` using the Read tool to check the last scan timestamp.

**Scan checks (run all, skip any that fail):**

1. **STATE.md transitions:** Read `.planning/STATE.md`. Compare key fields (phase, status, blockers) against the values in `scan-state.json`. If any changed:

• Phase completed: note "Phase N completed since last scan"
• New blocker: note "New blocker detected: [text]"
• Blocker resolved: note "Blocker resolved since last scan"

2. **ROADMAP.md structural changes:** Read `.planning/ROADMAP.md`. Compare the phase list against `scan-state.json`. If phases were added, removed, or reordered, note the changes.

3. **Plan-vs-summary diffs for completed phases:** If any phases completed since the last scan (detected in check 1), find their PLAN.md and SUMMARY.md files. Compare planned vs actual files, emergent work, and dropped items.

**After scanning, update `scan-state.json`** with current STATE.md values, ROADMAP.md phase list, and current timestamp. Write the updated file using Bash:

echo '{"last_scan_timestamp":"[ISO 8601]","state_md_snapshot":{...},"roadmap_phases":[...]}' > .planning/patterns/scan-state.json

**Append scan observations** to `.planning/patterns/sessions.jsonl` for each detected change. Each entry uses `"type": "scan"` and `"source": "scan"`.

If no changes detected, display:

### Monitoring Scan
No changes detected since last scan ([timestamp]).

If changes detected, display them as a compact section:

### Monitoring Scan
Changes detected since last scan:
- Phase 86 completed
- 1 plan-vs-summary diff (scope: expanded)
- ROADMAP.md: 1 phase status changed

If this is the first scan (no scan-state.json), display:

### Monitoring Scan
First scan -- baseline captured. Changes will be tracked from next session.

If `phase_transition_hooks` is `false`, skip this step entirely.

---

Step 2: GSD Position (SESS-01)

Read `.planning/STATE.md` using the Read tool.

**If STATE.md does not exist:** Display:

### GSD Position
No GSD project initialized. Run `/gsd:new-project` to get started.

Then skip to Step 3.

**If STATE.md exists, extract and display:**

• **Current Phase:** name and number (from the `Phase:` line under `## Current Position`)
• **Current Plan:** number and total (from the `Plan:` line, e.g., "02 of 5")
• **Status:** in progress, complete, blocked (from the `Status:` line)
• **Progress bar:** if present (the `Progress:` line with bracket notation)
• **Last activity:** date and description (from the `Last activity:` line)
• **Next action:** if listed in the `## Session Continuity` section (the `Next action:` line)

Format as:

### GSD Position

| Field          | Value                                          |
|----------------|------------------------------------------------|
| Phase          | 85 — Session Start + Slash Commands            |
| Plan           | 01 of 4                                        |
| Status         | In progress                                    |
| Progress       | [####____] 4/8 phases                          |
| Last activity  | 2026-02-12 — Completed plan 84-02              |
| Next action    | /gsd:execute-phase 85                          |

If any field is missing from STATE.md, omit that row rather than showing "N/A".

---

Step 3: Recent Activity (SESS-02)

Read `.planning/patterns/sessions.jsonl` using the Read tool.

**If the file does not exist or is empty:** Display:

### Recent Activity
No session history yet. Activity will be captured as you work.

Then skip to Step 4.

**If the file exists, parse the last 10 lines** (most recent entries). Each line is a JSON object with fields like: `type`, `timestamp`, `commit_type`, `message`, `files_changed`, `source`, `phase`.

Display as a compact table:

### Recent Activity

| Time                | Type   | Details                                            |
|---------------------|--------|----------------------------------------------------|
| 2026-02-12T14:30:00 | commit | feat(84-02): implement post-commit integration ... |
| 2026-02-12T14:15:00 | commit | test(84-02): add failing test for hook output ...  |

• **Time:** the `timestamp` field
• **Type:** the `type` field (commit, session, observation, etc.)
• **Details:** For commits: `commit_type(scope): message` truncated to 55 characters. For other types: `message` truncated to 55 characters.
• If entries span multiple days, add a date