From 0225214b0b45d68a20e512bbde79e906fa15749d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Calexvisualmakers=E2=80=9D?= Date: Mon, 30 Mar 2026 15:17:07 +0200 Subject: [PATCH] feat: Add granular feature status stages across all skills MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .claude/rules/general.md | 8 +++++++- .claude/skills/architecture/SKILL.md | 2 +- .claude/skills/backend/SKILL.md | 4 ++++ .claude/skills/frontend/SKILL.md | 4 ++++ .claude/skills/qa/SKILL.md | 7 ++++--- features/INDEX.md | 10 ++++++---- 6 files changed, 26 insertions(+), 9 deletions(-) diff --git a/.claude/rules/general.md b/.claude/rules/general.md index cec5631..a99377c 100644 --- a/.claude/rules/general.md +++ b/.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 diff --git a/.claude/skills/architecture/SKILL.md b/.claude/skills/architecture/SKILL.md index f0b495c..952b168 100644 --- a/.claude/skills/architecture/SKILL.md +++ b/.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: diff --git a/.claude/skills/backend/SKILL.md b/.claude/skills/backend/SKILL.md index a6e82b5..c23def0 100644 --- a/.claude/skills/backend/SKILL.md +++ b/.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." diff --git a/.claude/skills/frontend/SKILL.md b/.claude/skills/frontend/SKILL.md index f2f5bca..01dd74e 100644 --- a/.claude/skills/frontend/SKILL.md +++ b/.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] diff --git a/.claude/skills/qa/SKILL.md b/.claude/skills/qa/SKILL.md index c2f7022..333fbff 100644 --- a/.claude/skills/qa/SKILL.md +++ b/.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 ``` diff --git a/features/INDEX.md b/features/INDEX.md index 89f11d1..f90edd7 100644 --- a/features/INDEX.md +++ b/features/INDEX.md @@ -3,10 +3,12 @@ > Central tracking for all features. Updated by skills automatically. ## Status Legend -- **Planned** - Requirements written, ready for development -- **In Progress** - Currently being built -- **In Review** - QA testing in progress -- **Deployed** - Live in production +- **Planned** - `/requirements` done, spec written, architecture not yet designed +- **Architected** - `/architecture` done, tech design approved, ready to build +- **In Progress** - `/frontend` or `/backend` active or completed, not yet in QA +- **In Review** - `/qa` active, testing in progress +- **Approved** - `/qa` passed, no critical/high bugs, ready to deploy +- **Deployed** - `/deploy` done, live in production ## Features