new-featurelisted

# `/new-feature` — Feature pipeline orchestrator ## Why this is Form 2 (manual skill) Axis 2 (manual trigger) + axis 5 (procedural) + axis 8 (both). Form 1 rejected — user requested manual invocation. Subagent rejected — none of the three reasons apply (context, tools, model). A fixed-order procedure rules out a rule and CLAUDE.md. **Manual only.** `disable-model-invocation: true` hides this skill from the model: the `Skill` tool can't call it, and trying is blocked. When a conversation reaches the point of running it, print the exact command for the user to type — don't attempt the call. --- ## Contract **Ownership:** Feature zero→spec orchestrator. Owns the sequence, the input table, the spec lifecycle (`status:`), and the final output (`UC-NNN-spec.md`). Does **not** own the use case number or slug — `use-case-design` does. **Reads:** - `pom.xml`, `.claude/forbidden-imports.txt`, and this project's domain package, discovered and never assumed — validates the generated project - `docs/use-cases/UC-*/` — folder existence and each spec's `status:` line, by command - `docs/use-cases/UC-NNN-<slug>/*.md` — the partials of the case being run **Writes (indirectly via layer skills):** - `docs/use-cases/UC-NNN-<slug>/00-caso-de-uso.md` and `docs/use-cases/BACKLOG.md` — via `use-case-design` - `docs/use-cases/UC-NNN-<slug>/10-dominio.md` — via `domain-modeling` - `docs/use-cases/UC-NNN-<slug>/20-persistencia.md` — via `persistence-architect`, migration SQL included as a