---
name: Supervisor Checklist
slug: supervisor-checklist
category: Automation
description: Supervisor Checklist helps a factory supervisor load context, check EPICs, and confirm worker availability at the start of a session. It also includes coordination, planning, and closing steps for managing epic work.
github: "https://github.com/codingagentsystem/cas/tree/main/.claude/skills/cas-supervisor-checklist"
language: Rust
stars: 161
forks: 16
install: "npx degit https://github.com/codingagentsystem/cas/tree/main/.claude/skills/cas-supervisor-checklist ~/.claude/skills/cas-supervisor-checklist"
installs_to: ~/.claude/skills/cas-supervisor-checklist
source_path: .claude/skills/cas-supervisor-checklist/SKILL.md
collection_size: 7
category_size: 2226
collection_url: "https://dirskills.com/collections/codingagentsystem/cas"
added: 2026-09-08T05:36:10.830Z
last_synced: 2026-09-08T05:36:10.830Z
canonical_url: "https://dirskills.com/skills/supervisor-checklist"
---

# Supervisor Checklist

Supervisor Checklist helps a factory supervisor load context, check EPICs, and confirm worker availability at the start of a session. It also includes coordination, planning, and closing steps for managing epic work.

**Install:**

```bash
npx degit https://github.com/codingagentsystem/cas/tree/main/.claude/skills/cas-supervisor-checklist ~/.claude/skills/cas-supervisor-checklist
```

## README

# Supervisor Checklist

## Session Start

1. Identify yourself: `mcp__cas__coordination action=whoami`
2. Load EPIC/task context:
   ```
   mcp__cas__task action=list task_type=epic
   mcp__cas__task action=ready
   mcp__cas__task action=list status=blocked
   ```
3. Pull relevant memories and rules:
   ```
   mcp__cas__search action=search query="<keywords>" doc_type=entry limit=5
   ```
4. Check worker availability: `mcp__cas__coordination action=worker_status`

## During Coordination

Record decisions as you go:
```
mcp__cas__memory action=remember title="..." content="..." tags="decision"
```

## Epic Planning Checklist

- Every subtask has a `demo_statement` (if not, it may be a horizontal slice — restructure)
- Investigation tasks use `task_type=spike` with question-based acceptance criteria
- When multiple approaches exist, a spike with a fit check comparison in `design_notes` precedes implementation tasks

## Before Closing an EPIC

- Verify all worker branches are merged into the epic branch
- Confirm task deliverables exist on the epic branch
- Run full test suite on epic branch

## Session End

Store a short summary memory tagged `summary`.