quick-start

# Quick Start — MCP Task Orchestrator Interactive onboarding that teaches by doing. Detects your workspace state and adapts. ## Step 1: Detect Workspace State Resolve the project rootId first: check session context for a rootId injected by the SessionStart hook, or read `.taskorchestrator/config.yaml`'s top-level `project.rootId` (a file read, not an MCP call). Call the health check to determine which path to follow: ``` get_context() ``` When a rootId is known, pass it to scope the check to this project: `get_context(ancestorId="<rootId>")`. When no rootId is known — the common case for a truly fresh workspace, or one that hasn't been bootstrapped yet — call unscoped exactly as shown. **If no active or stalled items exist** — follow the **Fresh-Start Path** (Steps 2-8). **If active items exist** — follow the **Orientation Path** (Steps A-C). --- ## Step 1.5: Project Anchor Bootstrap (if needed) Before following either path, check whether this workspace has a project anchor yet: - If `.taskorchestrator/config.yaml` does not exist at all, skip this step — that's the truly fresh workspace covered by the Fresh-Start Path below. Bootstrap can happen on a later run once a config file exists (e.g., after `/manage-schemas` creates one). - If `.taskorchestrator/config.yaml` exists and already has a top-level `project:` block, read its `rootId` and use it for scoping throughout this session — no bootstrap needed. - If `.taskorchestrator/config.yaml` exists but has **no** `p...