dev

Use when starting work on features in a harness-based project. Triggers when user says "work on feature", "implement", "let's start coding", or references a feature ID (F001, F002). Enforces the session ritual (read progress, one feature, verify before/after, update progress, commit) and prevents batching multiple features.

Use when bootstrapping a new project in the monorepo that needs harness structure (init.sh, verify.sh, features.json, progress.txt). Triggers when user says "set up new project", "create project", "initialize", or "bootstrap". Prevents skipping harness components, inadequate feature granularity, and non-idempotent setup scripts.

Use when the feature list needs to evolve mid-project. Triggers when user says "split feature", "add feature", "re-prioritize", "audit features", "feature is too big", or when coding-session discovers a feature needs splitting. Provides protocols for adding, splitting, deprecating, and auditing features in features.json.

Use when given a task or context that requires deep codebase understanding before implementation. Triggers when user says "onboard", "understand this", "get up to speed", or provides task context that needs exploration first. Produces a comprehensive onboarding document in .claude/tasks/[TASK_ID]/.

Use when verify.sh fails repeatedly, a feature breaks unrelated code, or the project is in a bad state. Triggers when user says "tests are failing", "something broke", "revert", "recover", or "rollback". Provides a structured protocol for diagnosing failures, isolating regressions, and restoring the project to a known good state using git.