retro
Run the sprint boundary's cross-story review and retrospective, and propose AGENTS.md learnings as a diff.
- License 许可
- GPL-3.0
- 所属仓库
- bendusz/bstack
- 最近更新
- 2026-11-15
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- retro
- description
- Run the sprint boundary's cross-story review and retrospective, and propose AGENTS.md learnings as a diff.
- argument-hint
- [sprint-number]
03 SKILL.md 正文
If you were dispatched as a child agent (your task begins 'You are a bstack … child'), do not use this skill.
references/… below means ${CLAUDE_PLUGIN_ROOT}/skills/project-manager/references/…, and
<plugin> in any reference means ${CLAUDE_PLUGIN_ROOT}. Neither is a shell variable: write the
path out in every command.
Run the bstack:project-manager skill's procedure (load that skill first) for a sprint
retrospective. Load references/retro.md and follow it: the cross-story review, the three
questions, the AGENTS.md diff and the record are the whole contract.
Sprint: $ARGUMENTS (a sprint number; default is the lowest sprint whose stories are all merged,
or blocked and escalated, with no docs/retros/sprint-<n>.md yet)
Precondition: every story of that sprint is merged, or blocked and escalated, in its
pm-exec. Otherwise name the open stories and stop.
End with the review verdict, any fix or check stories for the next sprint (after the last sprint,
the corrective story or the user's ruling, as ## 1 says), the proposed
AGENTS.md diff or "no changes earned", and the path of the retro record. Then report to the user
and wait before decomposing the next sprint, unless the plan's Between sprints: is
autonomous.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /poteto:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
reflect
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.