Standup Sprint Kickstarters Checklist

Audience: project/product managers and sprint leads running a Stella Ops standup or sprint kickoff. Purpose: a repeatable checklist that turns each standup into an auditable, async-friendly event — readiness is evidenced, dependencies and blockers are owned, and the session leaves a signed, dated trail in the sprint file.

Use this alongside sprint task 22 (STANDUP-GAPS-300-019). Sprint structure and status discipline follow the implplan conventions in docs/implplan/AGENTS.md and the sprint template in the repo AGENTS.md (§6).

Before the standup

• [ ] Template aligned with the implplan conventions (Delivery Tracker, Execution Log, Decisions & Risks).
• [ ] Readiness evidence checklist filled in (dependencies, owners, SLOs).
• [ ] Dependency ledger captured with accountable owners.
• [ ] Async/offline workflow defined; time-box and exit rules noted.

During the standup

• [ ] Blocker metrics collected: blocker clear rate and blocker latency.
• [ ] Lint/check hook points identified for automation.

At standup close

• [ ] Execution Log updated.
• [ ] Decisions & Risks delta captured for the session.
• [ ] DSSE-signed standup summary stored with its UTC date.