reporting-workable-itemslisted
Install: claude install-skill HelixDevelopment/helix_constitution
# Reporting Workable Items (§11.4.202 · §11.4.148 · §11.4.171)
**A report that is only acknowledged is a lost requirement.** Answering "yes,
that's a bug, I'll look into it" in prose — without creating a tracked item — is
a §11.4.197 requirements-integrity violation: the requirement was accepted, then
silently evaporated. Every report becomes a **real, fully-populated, fully-synced
workable item**, or it is explicitly and honestly refused.
## The three report directives
| Directive | Use when | Resulting Type |
|---|---|---|
| `/helix:bug` (`/default-bug`) | A product **defect** — regression, user-visible broken behaviour | `Bug` |
| `/task` | An internal **workstream** — refactor, doc, infra, gate, audit | `Task` |
| `/issue` | **Anything trackable**, type not yet decided | classified into `{Bug|Feature|Task}` |
Note: the bare `/bug` collides with Claude Code's built-in — always use
`/helix:bug` or `/default-bug` (see the `action-prefix-system` skill).
## Classification is a closed set (§11.4.16)
`Bug` · `Feature` · `Task`. **There is no fourth type and no "Issue" type** —
`/issue` is an *entry point*, not a type. Inventing a type is a §11.4.16
violation.
- Classify from the report's own content, stated as **FACT** (§11.4.6 — never a
guess).
- If the content does not determine the type, **ASK** (§11.4.66 / §11.4.105)
before creating the item.
- Only when running autonomously where asking is impossible (§11.4.101), default
to the lowest-stakes `Task`, record the