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>
This commit is contained in:
@@ -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
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user