Smithery Logo
MCPsSkillsDocsPricing
Login
NewFlame, an assistant that learns and improves. Available onTelegramSlack
    staticwagomu

    scrum-event-sprint-planning

    staticwagomu/scrum-event-sprint-planning
    Planning
    6

    About

    SKILL.md

    Install

    • Telegram
      Telegram
    • Slack
      Slack
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    • Download skill
    ├─
    ├─
    └─
    Smithery Logo

    Give agents more agency

    Resources

    DocumentationPrivacy PolicySystem Status

    Company

    PricingAboutBlog

    Connect

    © 2026 Smithery. All rights reserved.

    About

    Guide Sprint Planning in AI-Agentic Scrum. Use when selecting PBI, defining Sprint Goal, or breaking into subtasks.

    SKILL.md

    AI Sprint Planning facilitator guiding teams through effective Sprint Planning. Single Source of Truth: `scrum.ts` in project root. Use `scrum-dashboard` skill for maintenance. 1 Sprint = 1 PBI - Select the top `ready` item No capacity planning - AI agents have no velocity constraints Instant events - No time overhead Choose the top `ready` item from Product Backlog.
    Before selecting, verify Definition of Ready:
    - Clear user story with role, action, benefit
    - Acceptance criteria specific and testable
    - Dependencies identified and resolved
    - No blocking questions remaining
    - Has executable verification commands
    
    Based on the PBI's benefit statement.
    Characteristics:
    - Evaluable: Can clearly determine if achieved
    - Stakeholder-Understandable: Meaningful outside the team
    - Outcome-Focused: Value delivered, not tasks completed
    - Fixed: Does not change during Sprint
    
    Working backwards - ask:
    - "What do we want to demonstrate at Sprint Review?"
    - "What would make stakeholders excited?"
    - "What can we show as a working increment?"
    
    Each subtask = one TDD cycle.
    Subtask format in `scrum.ts`:
    ```yaml
    subtasks:
      - test: "What behavior to verify (RED phase)"
        implementation: "What to build (GREEN phase)"
        type: behavioral  # behavioral | structural
        status: pending   # pending | red | green | refactoring | completed
        commits: []
        notes: []
    ```
    
    Subtask types:
    - `behavioral`: New functionality (RED → GREEN → REFACTOR)
    - `structural`: Refactoring only (skips RED/GREEN, goes to refactoring)
    
    Keep subtasks small (completable in one TDD cycle) Order by logical dependency Each subtask independently testable Update status immediately when completing Mark `type`: `behavioral` or `structural` "Complete all Sprint Backlog items" (not a goal) "Finish Stories A, B, and C" (output-focused) Goals only developers understand Sprint Goal input, Product Backlog prioritization Task breakdown, technical feasibility Facilitation, impediment removal

    A successful Sprint Planning produces shared understanding of WHY the Sprint matters, WHAT will be delivered, and HOW the team will achieve the Sprint Goal.

    Recommended Servers
    Browser tool
    Browser tool
    StudioMeyer-Crew
    StudioMeyer-Crew
    Agent News
    Agent News
    Repository
    staticwagomu/dotfiles
    Files