aidlc-sprint

Guides TDD-based sprint implementation with Jira or Linear context and CodeRabbit review triage.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill aidlc-sprint-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-sprint
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/aidlc/skills/aidlc-sprint
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill aidlc-sprint-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a sprint often means manually pulling ticket context, guessing at test coverage, and losing track of progress mid-implementation. This Skill automates the full sprint execution loop: it fetches work items from Jira or Linear, builds a TDD-focused plan, manages status transitions, and runs structured code reviews before merge. ## Core Features & Use Cases - Context Gathering: Fetches Sprint and Task details from Jira (via acli) or Linear, detects Task Spec vs user story formats, and extracts test scope comments. - TDD Planning: Generates test cases first, then implementation steps structured as Red-Green-Refactor cycles, with optional parallel sub-agents for multi-Task sprints. - CodeRabbit Review Integration: Runs automated code reviews with severity triage (Critical/Warning/Info), a 3-round fix loop, and adjudication of unresolved findings. - Status & Progress Management: Transitions Jira/Linear statuses, assigns tickets to the current user, and maintains a resumable progress ledger. - Use Case: Say "Start a sprint for PROJ-123" and the Skill fetches the ticket, plans tests, creates a feature branch, implements with TDD, and prepares reviewed commits for the MR. ## Quick Start Ask the assistant to start a sprint for a Jira issue key like PROJ-123 or a Linear issue ID like ENG-456.

Frequently Asked Questions about aidlc-sprint

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

FAQPage Schema
How do I start a sprint from a Jira ticket?

Provide a Jira issue key like PROJ-123 and the Skill fetches the issue via acli, extracts acceptance criteria and test scope, then builds a TDD plan. It also offers to transition the ticket to In Progress and assign it to you.

How does TDD sprint planning work with Linear issues?

The Skill detects Linear URLs or short IDs like ENG-456, fetches the issue and sibling Tasks via the Linear MCP, and derives a test plan from acceptance criteria or a Test Scope comment. Planning then follows the same Red-Green-Refactor cycle structure as Jira-backed sprints.

Does the CodeRabbit review work on Windows?

CodeRabbit has no native Windows build, so on Windows the Skill invokes the CLI through WSL using an absolute path. It detects the runtime once per session and normalizes WSL file paths before displaying findings.

Can I resume a sprint after an interruption?

Yes, the Skill maintains a progress ledger at .aidlc/sprint/<sprint-id>/progress.md. On restart it reads the ledger, treats completed tasks as done, and resumes at the first incomplete task or mid-fix-loop.

What happens if CodeRabbit is not installed?

The Skill presents a blocking choice: install and authenticate the CLI, explicitly skip reviews for the sprint (logged in the plan file), or cancel the sprint cleanly with no commits or status changes.

When should I use manual versus autonomous execution mode?

Manual mode pauses after each TDD cycle for approval and suits critical or uncertain areas. Autonomous mode runs all cycles after plan approval and fits well-understood, straightforward tasks.