Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    plan to issues

    1

    Convert remediation plans into traceable, template-aligned GitHub issues with dependency resolution and CLI automation.

    Free

    Security scanned
    plan to issues

    plan to issues

    Example session with this skill installed

    Transform the approved remediation plan in docs/remediation/action-plan.md into GitHub issues for the current repo. Ensure they use the 'bug' template for findings.

    • Read your context and instructions
    • Compiled the plan to issues

    I have analyzed the repository conventions and drafted the tickets based on docs/remediation/action-plan.md. I found two issue templates (bug.yml, feature.md) and matched 5 actions to the repository's existing labels.

    Ticket Draft Summary

    IDTitleTypeLabelsDependencies
    T-01[SEC-{number}] Fix SQL injection in auth.pybugsecurity, high-priorityNone
    T-02[SEC-{number}] Implement rate limitingbugsecurity, medium-priorityT-01
    T-03[SEC-{number}] Update crypto-js dependencybugmaintenanceNone
    T-04[SEC-{number}] Audit session middlewarebugsecurityT-01, T-02
    T-05[SEC-{number}] Document remediation stepsdocumentationdocsT-04

    Proposed New Labels:

    • security (Color: #d73a4a)
    • maintenance (Color: #a2eeef)

    The dry-run for docs/remediation/tickets.md was successful. I am ready to create these 5 issues in dependency order.

    Next steps

    1. Review the full ticket bodies in docs/remediation/tickets.md.
    2. Provide an explicit "yes" to create these issues on GitHub.
    3. Run dispatch-fixes once the tickets are live.

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

    About this skill

    Manually converting complex remediation plans into individual GitHub issues is prone to error, ID mismatches, and broken cross-references. This skill automates the transition from a static action plan to a fully traceable, dependency-aware backlog in your repository.

    What it does

    • Repo Analysis reads existing issue templates, labels, and milestones to ensure tickets match project conventions.
    • Dependency Mapping creates issues in the correct order and automatically resolves cross-ticket references once issue numbers are assigned.
    • Traceable Drafting preserves original finding IDs (F-nnn) and action IDs (A-nnn) within the generated GitHub issues for full auditability.
    • Smart Formatting applies zero-padded numbering to issue titles and headings (e.g., [ISSUE-017]) based on the assigned repository ID.
    • Safe Execution performs a dry-run validation and requires explicit user confirmation before any API calls are made to GitHub.

    How it works

    1. Context Discovery: The skill scans .github/ISSUE_TEMPLATE and repository labels using the gh CLI to identify local standards.
    2. Drafting: A dedicated script generates a tickets.md file mapping every planned action to a specific issue template.
    3. Dry-Run Validation: The create_issues.py script validates the ticket format and confirms the creation order without touching the API.
    4. Issue Creation: Upon user approval, the skill creates the issues, manages label creation, and updates the tickets file with live #number mappings.

    Frameworks & tools

    Built for environments with Python 3 and the GitHub CLI (gh). It integrates with standard GitHub issue templates (Markdown or YAML forms) and requires an authenticated session with appropriate repository permissions.

    Why this beats prompting it yourself

    Writing multiple tickets manually often leads to missing labels or broken links between related tasks. This tool enforces strict adherence to your existing .github templates and uses Python scripts to programmatically update cross-references that a standard LLM prompt would lose track of during bulk creation.

    Use cases

    • Converting a security audit or remediation plan into actionable engineering tickets.
    • Scaffolding a new project backlog from a high-level architecture document.
    • Migrating structured task lists from external documentation into GitHub.

    Known limitations

    Requires Python 3 and an authenticated GitHub CLI session. Deleting or closing issues in bulk via the script requires specific repository or organization-level permissions.

    Requires Python 3 and authenticated GitHub CLI. Bulk deletion requires organization-level 'Member privileges' for issue deletion. Integration depends on local ISSUE_TEMPLATE availability.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 12 days ago

    • Free with an Agensi account

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed12 days ago

    What's inside

    Frequently Asked Questions

    Convert remediation plans into traceable, template-aligned GitHub issues with dependency resolution and CLI automation.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use plan to issues on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Agents & Orchestration