| Human Note | Next Steps: in review phases may confuse user and lead them to run already run steps |
| Version | v4.4.0 |
| Skill | unit-test, bug-hunt, uat |
Bug Description
The completion banners in the review pipeline skills (unit-test, bug-hunt, uat) have hardcoded "Next steps" sections that suggest running stages that should already be complete or that come earlier in the pipeline. The banners appear to be copy-pasted from the review skill without adjusting for each skill's position in the pipeline.
The typical pipeline order is: review → unit-test → bug-hunt → uat
Current state:
| Skill |
Lines |
Next Steps Suggested |
Correct? |
review |
375-378 |
unit-test → bug-hunt → uat |
✅ Correct (entry point) |
unit-test |
396-399 |
bug-hunt, uat, review summary |
✅ Mostly correct (could omit uat since bug-hunt is the typical next step) |
bug-hunt |
447-450 |
unit-test, uat, review summary |
❌ Suggests unit-test (backwards; should already be done) |
uat |
434-437 |
unit-test, bug-hunt, review summary |
❌ Suggests both earlier stages (backwards; both should already be done) |
Notably, the uat skill itself enforces that unit-test must be complete before UAT can run (line 84-86 of uat/SKILL.md), yet the completion banner suggests running unit-test as a next step.
Steps to Reproduce
- Run
/rapid:uat <set-id> to completion
- Observe the completion banner suggests running
/rapid:unit-test and /rapid:bug-hunt as next steps
- These should already have been completed before UAT ran
Root Cause / Suggested Fix
The banners were copy-pasted from the review skill's completion banner without adjusting for pipeline position. Each skill should only suggest stages that come after it in the pipeline:
unit-test → suggest bug-hunt, then uat, then review summarybug-hunt → suggest uat, then review summaryuat → suggest review summary (final aggregation step); this is the last review stage
Workaround
Users can ignore the incorrect next-step suggestions and follow the pipeline order themselves.
Related Issues
None known.
Co-Authored-By: Claude Opus 4.6
Bug Description
The completion banners in the review pipeline skills (
unit-test,bug-hunt,uat) have hardcoded "Next steps" sections that suggest running stages that should already be complete or that come earlier in the pipeline. The banners appear to be copy-pasted from thereviewskill without adjusting for each skill's position in the pipeline.The typical pipeline order is:
review→unit-test→bug-hunt→uatCurrent state:
reviewunit-testreview summarybug-huntreview summaryuatreview summaryNotably, the
uatskill itself enforces that unit-test must be complete before UAT can run (line 84-86 ofuat/SKILL.md), yet the completion banner suggests running unit-test as a next step.Steps to Reproduce
/rapid:uat <set-id>to completion/rapid:unit-testand/rapid:bug-huntas next stepsRoot Cause / Suggested Fix
The banners were copy-pasted from the
reviewskill's completion banner without adjusting for pipeline position. Each skill should only suggest stages that come after it in the pipeline:unit-test→ suggest bug-hunt, then uat, then review summarybug-hunt→ suggest uat, then review summaryuat→ suggest review summary (final aggregation step); this is the last review stageWorkaround
Users can ignore the incorrect next-step suggestions and follow the pipeline order themselves.
Related Issues
None known.
Co-Authored-By: Claude Opus 4.6