design-start-sprint
Work the active sprint as visual-designer, with stories as GitHub issues. Answers brand questions addressed to visual-designer first (implementation waits on them), then finishes carried-over in-progress stories, then takes the visual-designer backlog in Rank order, one fresh design/ branch per story. Run once PM has activated the sprint; it also resumes a sprint already under way.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- design-start-sprint
- description
- Work the active sprint as visual-designer, with stories as GitHub issues. Answers brand questions addressed to visual-designer first (implementation waits on them), then finishes carried-over in-progress stories, then takes the visual-designer backlog in Rank order, one fresh design/ branch per story. Run once PM has activated the sprint; it also resumes a sprint already under way.
- allowed-tools
- Bash(.claude/bin/role:*) Bash(.claude/bin/sprint-state:*) Bash(.claude/bin/story list:*) Bash(.claude/bin/story show:*)
- disable-model-invocation
- true
02 资源文件 1
- 参考文档references/examples.md1.4 KB
03 SKILL.md 正文
Visual designer: work the active sprint
Preflight
- Run
.claude/bin/role require visual-designer ${CLAUDE_SESSION_ID}. If it fails, stop and tell the owner to run/role visual-designerfirst. Then confirm the repo has switched over:.claude/roles/_repo.mdhasstories: githubandsprints: project. If it doesn't, stop. This skill works the GitHub board. - Run
git fetch originand work fromorigin/main. Read.claude/skills/role/references/stories-on-github.md. - Run
.claude/bin/sprint-state. Unless it reportsstate: active, stop and report its output: PM hasn't activated a sprint yet. The active sprint iscurrent; its goal is in thecurrentsprint issue, and its stories arestory list --sprint <n>. - Read the repo's
CLAUDE.mdand your role file's session-start steps.
Brand questions first
Code never decides branding, so implementation stops on a story until you
answer. For every story in story list --sprint <n> (any lane), read the
thread (story show <ID> --comments 30) and find **For visual-designer:**
comments with no answer after them. For each:
- If the brand docs already decide it, reply citing
file#section(story comment <ID> --to <asking role> --body …). - If they don't and it's yours to decide (a spec detail, a token derived from
an approved decision), change the brand doc on a
design/branch, then reply with the PR and thefile#section. - If it's the owner's call (palette, type, marks, voice, direction), bring them one recommendation, then reply with their decision and the doc change.
Carryover
Then any of your stories that's already in-progress. Read it and its thread,
and finish only what's left. Don't redo what's already merged.
Then the backlog
Take story list --sprint <n> --lane visual-designer in Rank order: the first
story that's ready with every blocker (Blocked by:) at review or later.
For each story:
- use a fresh
design/<story-id>-<slug>branch fromorigin/main story start <ID>when you begin- use the skill the work calls for (
/brand-audit,/art-direction,/art-slot,/brand-qa seed) and meet the Acceptance criteria in the issue body exactly. A decision that's the owner's stays theirs: the PR asks for it as[PROPOSED P<n>]with a checkbox (the role's Proposals section). - put
Story: <ID>in the PR body and in a commit trailer, and label the PRrole:visual-designer. The merge moves the story toreview. Never move it there yourself. - once the PR is open, record what you verified:
story comment <ID> --record "Verification" --body-file <f>, citing commits and the outputs you looked at
If a story is wrong or can't be done as written, story comment <ID> --to architecture with what and why, and move on. Work that isn't in the sprint
goes to PM with story comment <ID> --to pm or a plain issue.
Stop
When nothing on your list can be picked up and no brand question is waiting, stop. Report the questions you answered, and what each remaining story is waiting on: the story, its status, and the blocker, comment, or the owner decision holding it.
04 同仓库更多 Skills
up-skill
Upstream skill, for when the dependency's job is asked for. Not for local work.
do-thing
Do the thing when asked to do the thing. Not for other things.
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).