document-selection

# Document Type Selection

This skill helps choose the right Metis document type for different kinds of work.

## Quick Decision Guide

**Is this work, or is it a decision?**
- Decision about architecture/approach → **ADR**
- Work to be done → Continue below

**Does this define WHY the project exists?**
- Yes → **Vision**

**Does this coordinate multiple capability increments?**
- Yes → **Strategy** (if Full preset enabled)

**Does this create a fundamental capability increment?**
- Yes → **Initiative**

**Is this a discrete, completable piece of work?**
- Yes, belongs to an initiative → **Task**
- Yes, standalone (bug/feature/debt) → **Backlog Item**

## Document Types Reference

| Type | Purpose | Parent Required |
|------|---------|-----------------|
| Vision | North star objectives | No |
| Strategy | Coordinated approaches | Vision (published) |
| Initiative | Capability increments | Strategy/Vision (published) |
| Task | Atomic work units | Initiative (decompose/active phase) |
| Backlog Item | Ad-hoc bugs/features/debt | No |
| ADR | Architectural decisions | No |

**Parent phase guidance:**
- Initiatives are typically created under a published vision
- Tasks are typically created under an initiative in decompose or active phase
- `reassign_parent` enforces initiative phase (must be decompose/active)

## User Terminology Mapping

When users request work items using common terms, map to Metis document types:

| User Says | Create |
|-----------|--------|
| "bug ticket", "bug", "defect" | `create_document(type="task", backlog_category="bug", ...)` |
| "feature ticket", "feature request" | `create_document(type="task", backlog_category="feature", ...)` |
| "tech debt ticket", "tech debt" | `create_document(type="task", backlog_category="tech-debt", ...)` |
| "project", "epic", "feature work" | Initiative (with parent) |
| "work item", "ticket" | Task (if has parent) or Backlog Item (if standalone) |

## When to Create Each Type

### Vision
Create when:
- Startin