| name | standup-prep |
| description | Help the user prepare a concise three-bullet standup note covering yesterday, today, and blockers before walking into the Daily Scrum. Invoke when the user needs a ~2-minute prep session immediately before their standup meeting. |
Originally authored for Agentic PM Kit (MIT).
When to use
Use this skill in the two minutes before the user's Daily Scrum meeting begins. Typical triggers include:
- The user is about to join their standup and wants to organize their thoughts quickly.
- The user has had a fragmented day and needs help articulating what was accomplished versus what is planned.
- A blocker has emerged and the user wants help stating it clearly so the right person can act on it.
This skill does NOT replace the standup meeting itself. It is a preparation tool only — the actual Daily Scrum is a team event that happens separately, in person or over video, and involves the full Scrum Team. This skill produces a personal note for the user; it does not conduct or substitute for the meeting.
Do not invoke for sprint planning, sprint review, or retrospective facilitation; those are separate events with distinct skills.
Summon the SME
Before facilitating, load the Scrum Guide reference on the Daily Scrum to ensure the prep note is aligned with its purpose.
Reading the config. Check .pm-kit.config.json for the sourcesMode field:
- If
sourcesMode is "online" (opt-in): fetch the URL stored at the key sources.scrumGuide in vendor/pm-kit/sources-index.json using your available web-fetch capability. Do not name a specific tool — use whatever your runtime provides. Navigate to the Daily Scrum section. Do not fabricate quotations or page numbers.
- If
sourcesMode is "offline" or the field is absent (the default): rely on your general knowledge of the Daily Scrum as defined in the 2020 Scrum Guide — a 15-minute daily event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Cite the canonical URL from vendor/pm-kit/sources-index.json at key sources.scrumGuide in the output. Do not fabricate quotations or page numbers.
In both cases, the URL to cite is https://scrumguides.org/scrum-guide.html.
Facilitation script
This is a fast, focused facilitation. Complete all steps in approximately two minutes. Do not expand or elaborate beyond what is useful for the standup.
Step 1 — Context check. Ask the user: "Which sprint are you in, and what is the sprint goal?" Use this to frame the prep note in terms of sprint progress, not personal task completion.
Step 2 — Yesterday. Ask: "What did you finish or meaningfully advance yesterday — stated in terms the team needs to know, not a granular task log?" Capture the answer in one to three bullet points. Prompt the user to connect the work to the sprint goal or to a specific story.
Step 3 — Today. Ask: "What are you committing to today?" Capture the answer as an intention, not a guarantee. One to two bullet points is typical.
Step 4 — Blockers. Ask: "Is anything preventing you from making progress — or at risk of blocking you today?" If yes, help the user name the blocker precisely and identify who needs to act on it. If no blockers, record "None."
Step 5 — Notes for the standup. Ask: "Is there anything you want to flag verbally in the standup that you don't need in the written note?" Capture brief prompts only — this section is a memory aid, not a formal record.
Step 6 — Save the artifact. Save the filled note to docs/pm-kit/outputs/standup-prep/<short-slug>.md. <short-slug> is a kebab-case ASCII slug (max 40 chars) derived from the date and person (e.g., 2026-04-20-luci). Confirm the final path with the user before writing. If the file exists, ask: overwrite, append a date suffix, or pick a new slug. The artifact begins with the three-line provenance header below (HTML comments, do not render):
<!-- Generated by agentic-pm-kit:standup-prep on YYYY-MM-DD -->
<!-- Languages: communication=<value>, output=<value> -->
<!-- Source mode: offline | online -->
Languages
The kit separates the language used for live agent–user dialogue from the language used in the saved artifact. Both values live in .pm-kit.config.json and are free-form strings — read each value verbatim, never infer a language from the conversation, and never select from a hardcoded list.
Facilitation dialogue. Speak to the user during facilitation in the language at language.communication. Use the string verbatim.
Filled artifact (saved TEMPLATE.md output). Produce the written artifact in the language at language.output. If language.output is absent or empty, fall back to language.communication.
Example values either field might contain: "en-US", "es-MX", "Português brasileiro", "Mandarin Chinese". Accept any string as given.
Acceptance gate
When the prep note is complete, point the user to CHECKLIST.md (sibling file) and ask them to verify each item. Remind them that the output must be marked PASS or FAIL. On FAIL, invite the user to return with specific notes so the note can be corrected before the meeting.
