Tier 2: CLAUDE.md-Driven Workflow

What You Get

Prerequisites

How CLAUDE.md Works

Example CLAUDE.md Snippets

Workflow Protocol

## MCP Task Orchestrator Conventions
- Use `create_work_tree` to create features with child items — never create items one at a time
- Use `advance_item(trigger=...)` for all role transitions — never update role directly via manage_items
- Call `get_context(itemId=...)` before starting work on any item to check gate status and expected notes
- Call `get_context()` (no params) at session start to see active and stalled work
- Use `get_next_item()` when uncertain what to work on next
- Fill required notes with `manage_notes(operation="upsert")` before attempting to advance phases
- Use `get_blocked_items()` to check for dependency blockers before starting an item

Session Resume

## Session Start
At the beginning of each session, call `get_context()` to see what's active, blocked, or stalled.
If resuming from a previous session, call `get_context(since="<last-session-timestamp>")` to see
recent transitions.

Dependency Awareness

## Dependencies
Before starting any item, check `get_blocked_items()` to confirm no upstream blockers.
When completing an item, check the `unblockedItems` field in the advance_item response
to see what's now ready to start.

Role Semantics

## Work Item Roles
- **queue** — planned but not started. Fill required queue-phase notes here.
- **work** — actively being implemented. Fill implementation notes.
- **review** — implementation complete, under review. Fill review notes.
- **terminal** — done. Items here are complete, cancelled, or archived.
- **blocked** — paused due to external dependency or manual hold.

CLAUDE.local.md for Personal Conventions

## My Preferences
- Default priority for new items: high
- When I say "TO", I mean Task Orchestrator
- Preferred complexity range: 3-7 (skip trivial and overly complex items)
- When creating features, always add a "test-strategy" child item

Team Scenario

Combining with Note Schemas

## Note Conventions
When creating a feature item, always fill these notes:
- `requirements` (role: queue) — what the feature must do
- `implementation-plan` (role: work) — how you'll build it
- `test-results` (role: review) — test output and coverage

When to Level Up