feature-implementation

# Feature Implementation Workflow End-to-end workflow for a `feature-implementation` tagged item — the **feature container** that holds the plan and holistic review. Child work items under this container use the `feature-task` tag with lighter gates (`task-scope` instead of the feature-level `feature-summary`, and no review phase by default — task-level review is opt-in via the `needs-task-review` trait, which adds a `review-checklist` note to that child). A second child-level trait, `needs-test-author`, is opt-in the same way (applied per the `/implement` Step 1 trigger rule) and adds its own gate-enforced notes. Covers all three phases (queue → work → review) with gate-enforced notes at each transition. **Usage:** `/feature-implementation [item-uuid]` - If `item-uuid` is provided: load the existing item and resume from its current phase - If omitted: create a new item and start from the beginning --- ## Phase 0 — Setup If an item UUID was provided, call: ``` get_context(itemId="<uuid>") ``` Check `canAdvance` and `missingRequiredNotes` to determine which phase the item is in, then jump to the appropriate phase below. If no UUID was provided, create the item: ``` manage_items( operation="create", items=[{ title: "<feature title>", tags: "feature-implementation", priority: "medium" }] ) ``` Note the returned UUID and `expectedNotes` list. Confirm the item is in `queue` role, then continue to Phase 1. --- ## Phase 1 — Queue: Define the Feature Summary **Goal:** ...