Arnold

Build — write code from docs with acceptance criteria verification

Plan — generate or refine feature specs, identify gaps

Review — critique docs for usability, product, and technical issues

Archive — move stale or reference docs to archive or reference folders

Arnold documentation-first development rules. Reference these rules when: (1) the user runs any /arnold: command, (2) docs/overview.md exists with Arnold's format (What We're Building / Core Features headers), (3) the user explicitly mentions Arnold, documentation drift, or spec alignment. Do NOT activate for projects that have a docs/ folder but no Arnold-generated content.

Bug — record a structured bug report in docs/issues/

Check — compare docs to code, find drift and gaps

Decide — record an architectural or product decision

Diff — quick drift summary without a full check

Feature — completeness matrix, deep feature status, or deep feature planning

Show available Arnold commands and usage guide

Initialize Arnold — scaffold docs for your project

Milestone — define and track phased work with feature rollup

Recap — start-of-session briefing, pick up where you left off

Resolve — fix drift items found by /arnold:check

Spec — decompose a spec document into Arnold's feature-based docs

Status — quick project overview

Update — sync docs after a coding session (use --quick for batch mode)