do-thing
Do the thing when asked to do the thing. Not for other things.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- do-thing
- description
- Do the thing when asked to do the thing. Not for other things.
02 资源文件 1
- 参考文档references/examples.md22 B
03 SKILL.md 正文
Steps.
04 同仓库更多 Skills
up-skill
Upstream skill, for when the dependency's job is asked for. Not for local work.
sre-start-sprint
Work the active sprint as SRE, with stories as GitHub issues. Observability review of the sprint's drafts first (architecture's contract review waits on it), then instrumentation verification for stories at review, then SRE's own backlog. Run once PM has activated the sprint; it also resumes a sprint already under way.
sprint-run
Plan the active sprint's role lanes and, once the owner confirms, start them in parallel. Reads the board, shows which stories and queues each role the repo runs as a lane (implementation, architecture, SRE, PM, and where the charters say so visual-designer and product) can pick up now and what everything else is waiting on, then runs one isolated `claude -p` session per lane (own worktree, role set, hooks on) via `.claude/bin/coordinator`, and reports from live state. Trigger on "run the sprint", "/sprint-run", "start the lanes", "what can the agents pick up", "kick off implementation and SRE". Not for working one story yourself (impl-start-sprint), activating or closing a sprint (pm-start-sprint, pm-close-sprint), or merging.
role
Set this session's role (e.g. pm, product, architecture, sre, implementation, visual-designer, or none) and load its charter, then start an optional task given after the role; or show the current role when run with no argument, or the repo's role catalog with `help`. The owner runs it at session start. Never invoke it on your own or to change roles mid-task.
release-review
Review a release's readiness across every delivery planner's board and repo (each feature's success signal, the milestones and stories delivering it, blockers and who owns them) and recommend go, no-go, or cut, written to docs/product/reviews/ (one file per review). Trigger on "/release-review", "where are we on R1", "are we ready to ship", "what's blocking the release", "go/no-go", and when a planner closes the last milestone a release names. Requires the product role. Not for sprint or cycle status (project-sync, producer-close-cycle), changing release scope (release-plan), or shipping or announcing anything (the owner).
release-plan
Define or re-cut the product's releases in docs/product/releases.md (each release's promise, audience, bet, features, cut line, success signals), drafting docs/product/vision.md first if it doesn't exist, then check that the delivery planners' milestones each target a release and hand the gaps to the planners once the plan merges. Trigger on "/release-plan", "what's in the first release", "plan the releases", "re-cut R2", "what comes after phase 1", "does the roadmap still serve the players". Requires the product role. Not for a single feature's definition (feature-brief), readiness of a release in progress (release-review), or sprint and cycle planning (pm, producer).