/arnold:init
Scaffold structured documentation for a new project - or an existing one.
When to use it
Starting a new project, or bringing Arnold into an existing codebase. Arnold asks what you're building and generates a docs/ folder organized by feature.
Usage
> /arnold:init
🦕 What are you building?
(You describe your project conversationally)
Scaffolding docs/ ...
📁 docs/
├── 📁 auth/
│ ├── auth-overview.md
│ ├── auth-flows.md
│ └── auth-criteria.md
├── 📁 booking/
│ ├── booking-overview.md
│ └── booking-criteria.md
├── 📁 payments/
│ └── payments-overview.md
├── decisions/
└── specification.md
✓ 3 features scaffolded, 7 doc files created
What it does
- Asks you to describe your product in natural language
- Identifies distinct features from your description
- For existing codebases, scans your code to extract what's already built
- Creates a
docs/folder with feature-based documentation - Generates overviews, flows, and acceptance criteria templates
💡 Tip
For existing projects, Arnold reads your code first and pre-fills docs with what it finds. No starting from scratch.
See also
- /arnold:plan - Flesh out docs with more detail
- /arnold:spec - Decompose an existing PRD
- Doc Structure - How Arnold organizes docs