Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 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.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed 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 scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Requires

    GitHub
    Example
    Azure
    Other
    Python
    Git

    Listedtoday

    What's inside

    Frequently Asked Questions