Convert issue tracker backlogs into prioritized execution sessions with test enforcement.
npx skills add https://github.com/alinaqi/maggy --skill maggy
Please help me install this Agent Skill. Skill: maggy Source: https://github.com/alinaqi/maggy/tree/main/skills/maggy Command: npx skills add https://github.com/alinaqi/maggy --skill maggy
Maggy solves the problem of turning a messy backlog of issues into consistently executed, quality-gated engineering work without breaking your normal Claude Code workflow.
Use Case: Your team has 50 open tickets across repos; Maggy prioritizes them, and you click Execute on the top ticket to spawn Claude Code with relevant architectural and prior-intent context for a test-enforced implementation.
Use the maggy skill to launch the local dashboard by running Maggy, configuring your issue tracker and codebase roots in ~/.maggy/config.yaml, and then starting the server so you can prioritize tickets and run Execute from the UI.
High-intent search queries and answers about installing and using this skill.
You prioritize issue tracker backlogs by ranking open issues using urgency, OKR alignment, and recency. This transforms messy backlogs into consistently executed, quality-gated engineering work across multiple codebases.
Context enrichment injects prior intents and symbols into your execution pipeline. It enables one-click ticket execution by spawning Claude Code with relevant context for test-driven implementation inside the correct repository.
Yes, ticket routing to local runs supports multiple codebases through validated working-directory routing. You configure codebase roots in a configuration file to ensure tickets execute in the correct repository environment.
You set up the local dashboard by configuring your issue tracker provider and codebase roots in a configuration file, then starting the local server. This enables ticket prioritization, one-click execution, and daily competitor briefings.
Yes, automated ticket execution spawns Claude Code with permissions suitable for automated file edits and command runs. It enforces a TDD pipeline inside the correct repo while maintaining your normal workflow.
Automated issue triage requires a configured issue-tracker provider and validated working-directory routing to function. Without proper configuration of codebase roots and context enrichment, the execution pipeline cannot spawn test-enforced sessions.
skullninjaImport tasks.md into the Coco tracker as an epic with dependencies.
adolfoaranaes12Execute approved task specifications sequentially with TDD and validation gates.
softmgCoordinate role-based pair programming sessions with automated testing and verification.
joshsmithxrmAutomate GitHub issue creation, triage, and grooming with PPDS conventions.
