feat: Add granular feature status stages across all skills

Replaces ambiguous 4-status system with 6 clear stages, one per skill:
Planned → Architected → In Progress → In Review → Approved → Deployed

- architecture: sets "Architected" (was "In Progress")
- frontend + backend: explicitly set "In Progress" with checklist items
- qa: sets "In Review" on start, "Approved" on pass (was only "In Review")
- general rules + INDEX.md: updated valid statuses and descriptions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/rules/general.md

@@ -48,7 +48,13 @@ After completing work on any feature, you MUST update tracking files. Follow thi
 
 **What to update in `features/INDEX.md`:**
 - Feature status column must match the feature spec header
-- Valid statuses: Planned, In Progress, In Review, Deployed
+- Valid statuses: Planned → Architected → In Progress → In Review → Approved → Deployed
+  - **Planned**: after `/requirements`
+  - **Architected**: after `/architecture`
+  - **In Progress**: after `/frontend` or `/backend` starts
+  - **In Review**: after `/qa` starts
+  - **Approved**: after `/qa` passes (no critical/high bugs)
+  - **Deployed**: after `/deploy`
 
 **NEVER do this:**
 - Do NOT say "I've updated the feature spec" without actually calling the Edit tool

.claude/skills/architecture/SKILL.md

@@ -90,7 +90,7 @@ Add a "Tech Design (Solution Architect)" section to `/features/PROJ-X.md`
 - [ ] Dependencies listed
 - [ ] Design added to feature spec file
 - [ ] User has reviewed and approved
-- [ ] `features/INDEX.md` status updated to "In Progress"
+- [ ] `features/INDEX.md` status updated to "Architected"
 
 ## Handoff
 After approval, tell the user:

.claude/skills/backend/SKILL.md

@@ -93,6 +93,10 @@ CREATE INDEX idx_tasks_status ON tasks(status);
 ## Checklist
 See [checklist.md](checklist.md) for the full implementation checklist.
 
+After completion, update tracking files:
+- [ ] Feature spec updated with implementation notes
+- [ ] `features/INDEX.md` status updated to "In Progress"
+
 ## Handoff
 After completion:
 > "Backend is done! Next step: Run `/qa` to test this feature against its acceptance criteria."

.claude/skills/frontend/SKILL.md

@@ -84,6 +84,10 @@ If no backend needed:
 ## Checklist
 See [checklist.md](checklist.md) for the full implementation checklist.
 
+After completion, update tracking files:
+- [ ] Feature spec updated with implementation notes
+- [ ] `features/INDEX.md` status updated to "In Progress"
+
 ## Git Commit
 ```
 feat(PROJ-X): Implement frontend for [feature name]

.claude/skills/qa/SKILL.md

@@ -101,14 +101,15 @@ If your context was compacted mid-task:
 - [ ] QA section added to feature spec file
 - [ ] User has reviewed results and prioritized bugs
 - [ ] Production-ready decision made
-- [ ] `features/INDEX.md` status updated to "In Review"
+- [ ] `features/INDEX.md` status updated to "In Review" (at QA start)
+- [ ] `features/INDEX.md` status updated to "Approved" (if production-ready) OR kept "In Review" (if bugs remain)
 
 ## Handoff
 If production-ready:
-> "All tests passed! Next step: Run `/deploy` to deploy this feature to production."
+> "All tests passed! Status updated to **Approved**. Next step: Run `/deploy` to deploy this feature to production."
 
 If bugs found:
-> "Found [N] bugs ([severity breakdown]). The developer needs to fix these before deployment. After fixes, run `/qa` again."
+> "Found [N] bugs ([severity breakdown]). Status remains **In Review**. The developer needs to fix these before deployment. After fixes, run `/qa` again."
 
 ## Git Commit
 ```

features/INDEX.md

@@ -3,10 +3,12 @@
 > Central tracking for all features. Updated by skills automatically.
 
 ## Status Legend
-- **Planned** - Requirements written, ready for development
+- **Planned** - `/requirements` done, spec written, architecture not yet designed
-- **In Progress** - Currently being built
+- **Architected** - `/architecture` done, tech design approved, ready to build
-- **In Review** - QA testing in progress
+- **In Progress** - `/frontend` or `/backend` active or completed, not yet in QA
-- **Deployed** - Live in production
+- **In Review** - `/qa` active, testing in progress
+- **Approved** - `/qa` passed, no critical/high bugs, ready to deploy
+- **Deployed** - `/deploy` done, live in production
 
 ## Features