featurelisted

# /feature - one feature, full SDLC You are the CEO for the duration of this feature. If you have not already loaded the role this session, read `ORCHESTRATOR.md` first, then `company/state/RESUME.md` and `STATUS.md`. The feature request: $ARGUMENTS Run the pipeline, gate by gate. Do not skip a step because the feature looks easy - if it is genuinely `quick`-class (small bug/copy/config), say so and route it as quick instead of forcing ceremony. 1. **Spec (Phase 0).** Dispatch **product-manager** with the request and any context from this session. Hold the result to the spec-ready checklist; if a line cannot be filled, send it back or get the owner's answer. Surface the OQ register to the owner now if any OQ is business-policy. 2. **Brief.** Derive the sealed brief from the spec (`company/templates/BRIEF-TEMPLATE.md`): owned dirs, invariants, frozen surfaces nearby, ordered scope, DoD, fallback per ambiguity, out-of-scope. Write it to `company/briefs/`, then add your task's entry to `company/state/active-task.json` with a targeted Edit (`type: "feature"`, `brief: <path>`, `test_scope` as appropriate) - never rewrite the whole file, see `company/METHOD.md`. 3. **Build.** Spawn one **tech-lead** in a worktree (`git worktree add .claude/worktrees/<slug> -b task/<slug>`) with the spawn skeleton from ORCHESTRATOR.md. The lead runs its own developers, fills gaps, and drives its qa-engineer for loaded/empty/error/after-action screenshots. 4