sprintix

Execute GitHub Project sprint items with dependency-ordered sequencing.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dduquenne/unanima-platform --skill sprintix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprintix
Source: https://github.com/dduquenne/unanima-platform/tree/main/.claude/skills/sprintix
Command: npx skills add https://github.com/dduquenne/unanima-platform --skill sprintix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sprintix addresses the difficulty of turning a sprint plan into concrete, traceable execution by continuously enforcing plan integrity and progress tracking across GitHub Projects.

Core Features & Use Cases

  • Convert a plan from GitHub Project into an actionable, per-issue execution sequence with guardrails and status updates.
  • Enforce ordering: critical dependencies are handled before features, with phase-based execution and automated checks.
  • Provide traceability and progress visibility through .sprint/sprint-N.md generation and status syncing with the GitHub Project.

Quick Start

Load the current sprint plan from the GitHub Project and start executing the next eligible issue.

Frequently Asked Questions about sprintix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute sprint plan items from a GitHub Project sequentially?

Sprint plan execution from a GitHub Project is automated by extracting issues, topologically ordering them by dependencies and priority, and generating a per-issue execution sequence with guardrails.

How does dependency ordering work for GitHub Project issues?

Dependency ordering for GitHub Project issues works by topologically sorting issues based on their dependencies and priority, ensuring critical path items execute before dependent features.

Can I track sprint progress and issue status automatically in GitHub Projects?

Sprint progress and issue status tracking in GitHub Projects is handled by generating a .sprint/sprint-N.md plan file with per-issue checkpoints and syncing status updates back to the project.

What's the best way to enforce phase-based execution for agile sprint plans?

Enforcing phase-based execution for agile sprint plans is achieved by applying automated checks and guardrails that ensure dependencies are resolved before features within grouped project phases.

Does sprint execution automation work with issues grouped into phases in GitHub Projects?

Sprint execution automation works directly with GitHub Projects where issues are grouped into phases, supporting both sequential and parallel execution according to the defined plan.

Why are some issues missing from my automated sprint execution sequence?

Issues missing from an automated sprint execution sequence are identified by extracting all plan data from the GitHub Project to ensure none are skipped during topological ordering and checkpoint generation.