Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    scrum master by Nissi

    1

    Transform technical plans into Jira or Azure DevOps backlogs with automated sprint planning and PR-gated story closure.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    scrum master by Nissi

    scrum master by Nissi

    Example session with this skill installed

    Review the technical plan in docs/arch.md and create a sprint backlog for the auth module in my local .scrum folder. Map these to Jira Cloud stories with acceptance criteria.

    • Read your context and instructions
    • Compiled the scrum master by

    I have analyzed docs/arch.md and decomposed the authentication module into a structured backlog. The plan is saved to .scrum/backlog_manifest.json and mapped to Jira Cloud hierarchy.

    Sprint Backlog: Authentication Module

    IDTypeTitleDependencyAcceptance Criteria
    AUTH-01StoryImplement JWT MiddlewareNone1. Validates RS256 signatures. 2. Rejects expired tokens. 3. Sets req.user context.
    AUTH-02StoryRefresh Token EndpointAUTH-011. Rotates refresh tokens on use. 2. Revokes compromised families.
    AUTH-03TaskConfigure .env.exampleNone1. Add AUTH_SECRET placeholder. 2. Update README setup steps.
    AUTH-04BugFix Cookie SameSiteNone1. Set SameSite=Strict for session cookies. 2. Verify across subdomains.

    Sprint Goal: Secure the API surface by implementing robust JWT validation and token rotation flows.

    Next steps

    1. Review the proposed stories in .scrum/backlog_manifest.json.
    2. Run python3 scripts/tracker_api.py --env-file .env check to verify Jira connectivity.
    3. Provide approval to publish these items to the Jira board.

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

    About this skill

    Managing a messy software backlog while trying to ship code is a constant friction point for developers. This skill bridges the gap between technical implementation plans and formal project management, turning your design docs and repository analysis into structured, traceable work items.

    What it does

    • Requirement decomposition breaks down technical analyses into epics, features, user stories, and granular tasks.
    • Backlog synchronization connects to Jira (Cloud/Data Center) or Azure DevOps to create or update work items using local credentials.
    • Sprint planning proposes sprint goals and orders work by dependencies, risk, and value based on project architecture.
    • Compliance gating enforces strict Definition of Done by preventing story closure until all related Pull Requests are approved.
    • Local state management maintains a .scrum/ directory with manifests and sync states to track progress without constant API calls.

    How it works

    1. Understand the skill reads your local repository files, existing architecture, and technical plans to define the scope.
    2. Map it identifies the specific hierarchy and field requirements of your target platform (Jira vs Azure DevOps).
    3. Plan the agent generates a sprint plan including a goal, sequence, and risk assessment stored in .scrum/.
    4. Publish using a local Python helper, it synchronizes the plan to your project board while respecting .env security.

    Frameworks & tools

    Built for teams using Jira Cloud, Jira Data Center, or Azure DevOps. It utilizes a python3 helper script for REST API interactions and integrates with standard Git workflows for PR-based story closure.

    Why this beats prompting it yourself

    Writing valid Jira stories with proper acceptance criteria and parent-child links is tedious and error-prone. This skill automates the boilerplate, maintains a local source of truth in your repo, and enforces a hard link between code approval and task completion that generic prompts miss.

    Use cases

    • Initial project scaffolding to turn a new README or design doc into a full Jira backlog.
    • Sprint preparation to group existing tasks into a coherent sprint goal with dependency mapping.
    • Automated tracking to update task statuses and verify PR approvals before closing PBIs.
    • Cross-platform migration to map conceptual requirements to platform-specific work item types.

    Known limitations

    Requires local Python 3 and a configured .env file for remote synchronization. It does not support automatic deletion of items or reassigning work belonging to other users.

    Requires local Python 3. Supported providers limited to Jira and Azure DevOps via REST. Cannot start/close sprints or reassign others' work. Credentials must be provided in a local .env file.

    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 28 days ago

    Requires

    GitHub
    Example
    Azure
    Other
    Python
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    example.test
    dev.azure.com
    api.github.com
    other.test
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    The skill creates a `.scrum/` directory in your project to track sync states and manifests locally, ensuring your repository remains the source of truth for the backlog. This allows for offline planning and prevents duplicate work items when syncing to Jira or Azure DevOps.

    This skill is compatible with Jira Cloud, Jira Data Center, and Azure DevOps. It requires a local Python 3 environment and a `.env` file to securely handle your platform credentials and API tokens.

    Unlike generic prompts, this skill enforces a 'PR-gated' workflow, meaning it validates that all associated Pull Requests are approved and merged before a story can be closed, ensuring your board reflects the actual state of the code.

    Yes, the skill is designed to read your existing READMEs, design documents, and repository architecture to automatically decompose high-level plans into structured epics, stories, and tasks.

    For security and data integrity, the skill does not support the automated deletion of work items or the reassignment of tasks belonging to other team members.

    New in Business & Operations