cc-featurelisted

# Feature Workflow Feature request: $ARGUMENTS ## Step 1 — Task Card validation (task-coach) Invoke `task-coach` with the feature description above. task-coach must produce a complete Task Card before any other agent runs. The Task Card is ready when it contains: title, type, risk classification, scope, context, acceptance criteria, and constraints. If any field is missing or ambiguous, task-coach must ask one clarifying question at a time and wait for the answer. Do not proceed with an incomplete Task Card. **STOP here. Show the completed Task Card and wait for human confirmation before continuing.** --- ## Step 2 — Technical Plan (architect) Invoke `architect` with the validated Task Card from Step 1. architect must produce a Technical Plan that covers: - Chosen approach and rationale - Affected files and modules - Data model changes (if any) - API contract changes (if any) - Identified risks and mitigations - Open questions that require a human decision **STOP here. Show the Technical Plan and wait for explicit human approval. Do not invoke implementer until the plan is approved.** --- ## Step 3 — Implementation (implementer) Invoke `implementer` with the approved Technical Plan and the Task Card. Implementer creates a Git Worktree before touching any file; all edits happen inside it. implementer must: 1. Read the Technical Plan before touching any file 2. Apply the minimal diff — only what the plan specifies 3. Run the project test suite after implementat