aidlc-elaborate

Decompose approved features into Epics and Sprint groupings using Mob Elaboration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Breaking an approved feature into well-scoped Epics and Sprints is slow and inconsistent when done manually. This Skill automates the AI-DLC Mob Elaboration ritual, proposing Epic boundaries, Sprint groupings, and team-size recommendations with human approval gates before anything is published. ## Core Features & Use Cases - Parallel Theme Analysis: Spawns subagents per theme cluster to propose Epic boundaries, indicative work items, dependencies, and risks, then consolidates results. - Multi-Backend Publishing: Creates Epic documentation in GitLab (markdown files with MR review), Linear (native Projects), or Confluence (pages with Jira integration). - Ceremony Scaling: Adjusts depth by gear — Quick skips decomposition, Standard keeps hierarchy without the ritual, Deep runs the full four-phase Mob Elaboration. - Use Case: After a feature intent is approved, run the Skill to decompose an authentication feature into Epics like "Identity Provider Integration" and "Session Management", grouped into Sprints with a team-size recommendation, then publish to GitLab after explicit approval. ## Quick Start Ask the assistant to decompose the approved authentication feature into Epics and Sprint groupings using the aidlc-elaborate skill.

Frequently Asked Questions about aidlc-elaborate

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

FAQPage Schema
How do I break down a feature into Epics and Sprints?

Run the aidlc-elaborate skill on an approved Feature artifact. It identifies 3-5 theme clusters, spawns parallel subagents to propose Epic boundaries and indicative work items, then groups them into Sprints with phase and lane assignments for your review.

Does aidlc-elaborate create Jira tickets or tasks?

No. This skill creates Epics only. Task Specifications are generated later in /aidlc-design after ADRs and the domain model exist, and Jira transfer happens in /aidlc-verify after design and verification.

Which backends does aidlc-elaborate support?

It supports GitLab (markdown files with MR-based review), Linear (native Projects linked to Initiatives), and Confluence (page hierarchies with Jira integration). The backend is auto-detected from the Feature artifact's frontmatter, Initiative URL, or page ID.

Will the skill publish Epics without my approval?

No. A hard publish gate applies at every ceremony gear. The skill drafts Epics and Sprint groupings in chat first and only writes to GitLab, Linear, or Confluence after you explicitly reply with approval such as "publish" or "go ahead".

What is the difference between Quick, Standard, and Deep ceremony gears?

Quick skips decomposition when the Feature Brief already carries one obvious task. Standard keeps the Epic-Sprint-Story hierarchy but drops the four-phase ritual. Deep runs full Mob Elaboration with parallel theme agents, Epic docs, and approval gates.

What prerequisites are needed before running feature decomposition?

The Feature artifact must exist and show approved status: a GitLab markdown file with status approved, an active Linear Initiative, or a Confluence page showing Feature approved. If missing, the skill offers to run /aidlc-intent first.