/arnold:spec
Decompose an existing PRD or spec into Arnold's feature-based doc structure.
When to use it
When you have an existing specification document (PRD, Google Doc, requirements file) and want to convert it into Arnold's feature-based format. Arnold reads the spec, identifies feature areas, and creates the corresponding doc folders.
Usage
> /arnold:spec
🦕 ARNOLD SPEC DECOMPOSE
━━━━━━━━━━━━━━━━━━━━━━━━
Paste or describe your spec, PRD, or requirements doc.
(Analyzing PRD structure...)
Found: 5 feature areas, 3 non-functional requirements
Mapping to Arnold doc structure...
→ auth/ (extracted from sections 2.1, 3.4)
→ booking/ (extracted from sections 1.1, 1.2, 4.1)
→ payments/ (extracted from section 5)
→ calendar-sync/ (extracted from section 6)
→ accounts/ (extracted from sections 2.2, 3.1)
✓ PRD decomposed into 5 feature doc folders.
What it does
- Takes an existing specification or PRD as input
- Identifies distinct feature areas within the spec
- Maps spec sections to Arnold's feature folder structure
- Creates doc files with content extracted from the original spec
💡 Tip
Use /arnold:spec for existing specs. Use /arnold:init for new projects where you describe what you're building conversationally.
See also
- /arnold:init - Scaffold docs for a new project
- /arnold:plan - Flesh out docs after decomposing