aidlc-help

Explains AI-DLC methodology, workflow phases, and available planning skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams adopting the AI-Driven Development Lifecycle (AI-DLC) often struggle to understand its methodology, artifact hierarchy, and which planning skill to invoke at each stage. This Skill provides on-demand guidance explaining the methodology, the five-phase workflow, and how to get started. ## Core Features & Use Cases - Methodology Explanation: Describes the 10 key AI-DLC principles, core artifacts (Project, Feature, Epic, Sprint, Task), and concepts like Mob Elaboration and Project Context Grounding. - Workflow Guidance: Maps the full planning pipeline from /aidlc-intent through /aidlc-elaborate, /aidlc-design, /aidlc-verify, and /aidlc-sprint, including Jira hierarchy and Confluence integration. - Troubleshooting: Answers common blockers such as missing Confluence documents, unapproved Features, and incomplete phase prerequisites. - Use Case: A developer asks "How do I start planning a new feature?" and receives a recommendation to run /aidlc-intent along with what inputs and approvals are needed. ## Quick Start Ask the assistant to explain what AI-DLC is and which planning skill to use for starting a new feature.

Frequently Asked Questions about aidlc-help

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

FAQPage Schema
What is AI-DLC and how does it differ from traditional development?

AI-DLC is an AI-Driven Development Lifecycle methodology from AWS where AI proposes plans and humans approve them, reversing the traditional human-initiates, AI-assists model. It integrates DDD, BDD, and TDD as core practices with short Sprints lasting hours to days.

How do I start planning a new feature with AI-DLC?

Start with /aidlc-intent, which gathers requirements through clarifying questions, drafts a Feature document, creates a Confluence page for team review, and optionally creates a Jira Project for portfolio tracking.

What is the difference between an Epic and a Sprint in AI-DLC?

An Epic is a cohesive work grouping similar to a DDD subdomain, created with the aidlc:epic label. A Sprint is a short iteration of hours to days that groups related Tasks within an Epic, unlike multi-week Scrum sprints.

Why does /aidlc-elaborate say my prerequisites are incomplete?

The elaborate phase requires an approved Feature document in Confluence. Check the Workflow Status table in your Confluence doc and obtain stakeholder approval for the Feature before proceeding to decomposition.

Can I skip the Confluence phase and go straight to Jira?

Skipping is possible with explicit override, but Confluence-first is recommended for team collaboration, comment resolution before Jira creation, and traceability between artifacts. Jira transfer happens in /aidlc-verify after an 80% confidence check.