# Session Start

> Start a session by loading workspace context and prior state.

- Skill: `majiayu000/session-start-4` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/session-start-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/session-start-4/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/session-start-4

---


# Session Start

The Orchestrator drives this workflow, loading context directly — session operations run inline because they need conversation context and judgment. Orchestrator reads workspace files and prior session state, then establishes the session goal.

**Prerequisites:** Access to workspace configuration files.

---

## Phase 1: Load Context

Read workspace files and check for prior sessions.

### Steps

1. Read `workspace.config.yaml` — process profile, forge topology, board IDs, AI runtimes, commands
2. Read `docs/workspace/context.md` — tech stack, domain terms, architecture, key conventions
3. Read `docs/workspace/goals.md` — durable priorities, milestones, backlog (if exists)
4. Read `.tmp/workspace/goals.md` — active sprint state, current focus (if exists)
5. List files in `.tmp/sessions/` — read the most recent handoff artifact if any exist
6. Note any incomplete work or open questions from prior sessions

### Verify Board Status

For any tracked issues carried over from prior sessions or identified in sprint state:

1. Read `workspace.config.yaml` for board field IDs
2. Check current board status for each active issue
3. Flag any stale statuses (e.g., issue still "In Progress" but branch was merged)
4. Correct stale statuses before proceeding

---

## Phase 2: Establish Session

Summarize context and confirm the goal.

### Steps

1. State the process profile and its implications
2. Note active AI runtimes
3. Identify current priorities from goals.md
4. Flag any carry-over from prior sessions
5. Confirm the session goal with the user

### Output

```markdown
## Context Anchors

- **Issue:** #<number> - <title> (if applicable)
- **Branch:** <active branch> (if applicable)
- **Prior Session:** <session file> (if applicable)

## Session Context

**Process Profile:** <lightweight | standard | regulated>
**AI Runtimes:** <list>
**Active Priorities:**

- <priority 1>
- <priority 2>

## Carry-Over (if any)

- <incomplete item from prior session>

## Session Goal

<Clear statement of what this session aims to accomplish>

## Next Step

<First action toward the goal>

**Approval Required:** Yes
```

### ⛔ CHECKPOINT

**STOP.** Confirm the session goal before proceeding to execution.

---

## Error Handling

| Situation                     | Recovery                            |
| ----------------------------- | ----------------------------------- |
| workspace.config.yaml missing | Ask user to run setup-workspace     |
| goals.md missing or empty     | Ask user for current priorities     |
| Prior session file is stale   | Verify current state before acting  |
| Context files are outdated    | Use refresh-context skill to update |