メニュー
Generate a structured team assignment message from the current sprint plan. Produces a copy-pasteable message for Slack, email, or team chat with per-person assignments, context blocks, and key ground rules. Use after sprint-plan to share assignments.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sprint-assign |
| description | Generate a structured team assignment message from the current sprint plan. Produces a copy-pasteable message for Slack, email, or team chat with per-person assignments, context blocks, and key ground rules. Use after sprint-plan to share assignments. |
| allowed-tools | Read, Glob, Grep |
| user-invocable | true |
Generate a shareable team assignment message from the current sprint plan.
/sprint-plan has created or updated the plan$ARGUMENTS can be:
Look for the sprint plan in:
.claude/plans/ — plan mode files (most recent by modification time)docs/sprint-plan.md, maxwell/docs/next-steps.md)/sprint-plan first."For each assigned feature in the plan, read its docs/features/{id}/idea.md to pull:
Format a message with this structure:
**[Project Name] Sprint — [Date Range]**
[1-2 sentence context: what's the driving event, what does success look like]
All features tracked in `docs/features/DASHBOARD.md`. Use `/feature-plan <id>` to generate your implementation plan before starting. Branch off `[branch-name]`, PR back into `[branch-name]`.
---
**[Senior Dev Name] — [Lane]**
- `feature-id` (Priority, Effort) — what to do
- `feature-id` (Priority, Effort) — what to do
**[Junior Dev Name] — [Lane]**
- `feature-id` (Priority, Effort) — what to do
- Feeds into: [which senior dev's work this supports]
[repeat for each team member]
---
**Key context for everyone:**
- [Branch strategy — which branch to work from]
- [Architecture context — key decisions they should know]
- [What's already done — don't re-do this]
- [Where to find docs — entry point for onboarding]
- [Questions → who to ask]
Show the message and ask:
Use to create or update the per-author Ghost style guide from all available signals — interview answers, reference docs, and the published corpus — and to fold a newly approved post into it. Triggers on "build my style guide", "update the style guide", "learn my voice from my posts", and is invoked by push-draft after a successful push.
Use to write the first full draft of a Ghost blog post locally, matching the author's style guide, then self-audit it against the anti-pattern checklist. Triggers on "draft a post about X", "write the first draft", "start a new blog post".
Use to revise an existing local Ghost draft section by section with the author, improving formatting, voice, and accuracy. Triggers on "revise this post", "let's go through it section by section", "tighten this draft".
Use when first connecting a project to a Ghost site for the ghost plugin, or whenever Ghost credentials are missing/unverified — onboards the Ghost Admin API key, enables the plugin at project level, and verifies the connection. Triggers on "set up ghost", "connect my ghost site", "ghost credentials", "the ghost mcp isn't working".
Use to push a finished local Ghost draft to the Ghost site as a draft (never published) — pull-guards against in-editor edits, uploads the feature image, creates or updates the post, verifies links, and feeds the approved post back into the style guide. Triggers on "push this to ghost", "send the draft to ghost", "publish to ghost as a draft".
Use to write a Ghost blog post end to end, walking the full plan→draft→revise→push flow in one guided pass. Triggers on "write a post about X end to end", "take this from idea to a ghost draft", "guide me through writing a post".