Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Scrum Delivery

    1

    Maintain a strict markdown delivery board that enforces WIP limits and tracks ship-ready status for product slices.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Scrum Delivery

    Scrum Delivery

    Example session with this skill installed

    Update the board for project 'Harbor-Desk'. Set task T-002 to in-flight. The slice goal is 'Basic CRUD for tickets'. Current WIP limit is 1. T-001 is already done.

    • Read your context and instructions
    • Compiled the scrum delivery

    I have updated the delivery board for Harbor-Desk. Task T-001 is marked as done, and T-002 has transitioned to in-flight. The WIP count remains at 1, which satisfies the current limit.

    Delivery Board: Harbor-Desk

    Product: Harbor-Desk
    Slice Goal: Basic CRUD for tickets
    WIP Limit: 1
    WIP Now: 1
    Event: start-task (T-002)
    Status: ready

    Ships

    • Goal: Basic CRUD for tickets
    • Ships: not yet
    • Required P0s: T-001, T-002, T-003

    Phases

    Phase IDStatus
    phase-authdone
    phase-crudin-progress

    Tasks

    Task IDTitleStatusWIP
    T-001Create ticket schemadone
    T-002Implement POST /ticketsin-flight*
    T-003Implement GET /ticketsqueued

    Blockers

    none

    WIP Tracking

    • WIP Now: 1 / 1
    • In-flight Tasks: T-002

    Not This Slice

    • P1: Ticket attachments
    • P2: Bulk delete

    Refused

    • tracker: no
    • story-points: no

    Residual

    • implemented: no
    • tracker: no

    Next steps

    • Run junior-tdd to implement the logic for T-002.
    • Execute qa-engineer once the task is ready for verification.
    • Update the phase plan to reflect the progress in phase-crud.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Development teams often lose track of what is actually shipping in a specific slice, leading to WIP bloat and "Jira cosplay" where boards show progress but the product remains broken. Projects stall when blockers are vaguely defined without clear owners or next steps.

    What it does

    • Maintains a single-source-of-truth markdown board for a specific product slice.
    • Strictly enforces WIP limits to prevent file collisions and context switching.
    • Validates that all P0 tasks are complete or explicitly blocked before allowing a "ship" status.
    • Maps blockers to specific "sibling" roles like junior-tdd or qa-engineer to ensure clear handoffs.
    • Tracks phase status and task progression without the overhead of hosted project management tools.

    Why this beats prompting it yourself

    Manually prompted agents often hallucinate velocity charts, invent story points, or attempt to start implementation tasks themselves. This skill enforces a strict contract that prevents "implementation creep" and ensures the board follows reality rather than leading it.

    Use cases

    • Enforcing a one-task-at-a-time limit for LLM coding agents to prevent merge conflicts.
    • Generating a transparent, readable status file for conductors to audit project health.
    • Identifying exactly which agent role is holding up a delivery phase with ownership-based blockers.

    Known limitations

    This skill only manages a single product slice at a time and does not support multi-product boards or long-term sprint archives. It requires a pre-existing phase plan and task list to function.

    Requires project_path, phase_plan_path, and tasks_path to exist. Does not integrate with external SaaS trackers like Jira or Linear. Supports one product slice per board.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Write Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill acts as a strict orchestrator that prevents "WIP bloat" by enforcing hard limits on active tasks, ensuring your agents finish one feature slice completely before moving to the next.

    The Scrum Delivery skill is compatible with any AI agent or 'conductor' capable of reading and writing markdown files, making it ideal for multi-agent coding workflows.

    When a task is blocked, the skill requires you to assign a specific 'sibling' role (e.g., QA or TDD) as the owner, creating a clear audit trail for handoffs.

    You will receive the core skill configuration, documentation on the required markdown schema, and a template for initializing your first product slice board.

    No, this skill is designed for high-velocity, single-slice delivery; it manages one product slice at a time to maintain focus and prevent implementation creep.

    Setup is straightforward: you provide an initial phase plan and task list, and the skill initializes a standardized markdown board to begin tracking execution.

    New in Workflow Automation