Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-story-done
saas-story-done
UnverifiedVerify story acceptance criteria, test evidence, and ADR alignment before marking Complete.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.6 KB |
| agents/openai.yaml | config | 43 B |
| references/review-gates.md | markdown | 2.4 KB |
| references/sprint-next.md | markdown | 1.5 KB |
| references/tech-debt-row.md | markdown | 1.3 KB |
references/sprint-next.md
View on GitHub# Phase 8: The next story when a sprint plan exists
Read only when `production/sprints/` holds a sprint plan.
1. Read the newest sprint plan in `production/sprints/`.
2. Find the stories that are Ready or Not Started, not waiting on an unfinished
story, and in the Must Have or Should Have tier.
```
### Next Up
The following stories are ready to pick up:
1. [Story name] — [one line] — Est: [estimate]
2. [Story name] — [one line] — Est: [estimate]
Run `/saas-story-readiness [path]` to confirm a story is ready before starting.
```
**Every Must Have story Complete or Blocked:** print the close-out sequence.
```
### Sprint Close-Out Sequence
All Must Have stories are complete. QA sign-off is required before advancing.
1. `/saas-smoke-check sprint` — the critical path still works end to end
2. `/saas-team-qa sprint` — test case execution, bug triage, sign-off report
3. `/saas-retrospective` — what went well, what didn't, action items
4. `/saas-gate-check` — only when advancing a stage, after `/saas-team-qa` returns
APPROVED or APPROVED WITH CONDITIONS
5. `/saas-sprint-plan new` — the next sprint
```
Should Have stories still unstarted: list them beside the sequence, so the user can
close the sprint now or pull in more work.
**No story ready, Must Have stories still In Progress:** "No more stories ready to
start — [N] Must Have stories still in progress. Finish those before the sprint
close-out."
The checkpoint's **Next step** names the same story or step the user is shown.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |