aidlc-progress

Generate confidence, risk, and progress assessments for AI-DLC projects across GitLab, Linear, or Confluence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams running AI-DLC workflows lack a unified way to measure project health across documentation, work tracking, and code. This Skill produces a consolidated confidence, risk, and progress report so stakeholders can see where a project stands and what needs attention. ## Core Features & Use Cases - Two Assessment Modes: Full Assessment covers documentation quality, team readiness, execution evidence, and code health; Execution Assessment focuses on epics and sprints with complexity-vs-coverage analysis of completed work and estimation confidence for pending work. - Multi-Backend Support: Automatically detects and works with GitLab (markdown files), Linear (Initiatives/Projects/Issues), or Confluence (pages with Jira), at any phase from planning through implementation. - Parallel Sub-agent Assessment: Spawns specialized assessors for documentation, work tracking, code health, completed work, and pending work, then consolidates results into weighted Confidence and Risk scores with a visual dashboard and machine-readable JSON. - Use Case: Ask "How are we doing on PROJ-123?" mid-sprint to get an execution assessment showing which completed sprints have unmitigated complexity and which pending sprints carry high estimation risk. ## Quick Start Ask the assistant to check the progress of your project by providing a GitLab branch, Linear initiative URL, Confluence page URL, or Jira key, then choose Full or Execution assessment when prompted.

Frequently Asked Questions about aidlc-progress

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

FAQPage Schema
How do I check project progress with AI-DLC?

Provide a project reference such as a GitLab feature branch, Linear initiative URL, Confluence page URL, or Jira key, then choose Full or Execution assessment mode. The skill detects the backend and phase automatically and returns a dashboard with confidence, risk, and progress metrics.

What is the difference between Full and Execution assessment modes?

Full Assessment covers documentation quality, team readiness, execution evidence, and code health for overall project readiness. Execution Assessment focuses on epics and sprints, analyzing completed work complexity versus test coverage and pending work estimation confidence.

Does aidlc-progress support Linear and Confluence backends?

Yes, it supports GitLab markdown files, Linear Initiatives/Projects/Issues, and Confluence pages with linked Jira issues. The backend is detected automatically from the provided reference rather than selected manually.

How does the execution assessment measure delivery risk?

It computes an unmitigated complexity score per sprint by subtracting coverage score from complexity score, and assesses pending sprints for estimation confidence and unknowns such as vague acceptance criteria, undefined integrations, and unresolved dependencies.

What tools does the progress assessment use to fetch data?

It prefers CLI tools like acli for Atlassian, glab for GitLab, and gh for GitHub because they use fewer tokens, falling back to Atlassian, GitLab, and Linear MCP servers when CLIs are unavailable.