AI-DLC Mob Elaboration FAQs

Question 1

Does this skill automatically create Jira tickets?

Accepted Answer

No. Following the AI-DLC methodology, this skill focuses on documentation and review in Confluence first. Jira ticket creation is handled later in the process via the /aidlc-verify skill.

Question 2

How does the skill handle complex dependencies?

Accepted Answer

It performs a detailed dependency analysis, classifying every task as either 'blocking' or 'non-blocking' and identifying which environment (dev vs. deploy) the dependency applies to.

Question 3

Can I review the AI's decomposition before it's finalized?

Accepted Answer

Yes. The skill includes a 'Human Review' phase where the team uses Confluence comments to provide feedback, which the AI then addresses in a follow-up resolution session.

Question 4

What are 'Bolts' in the context of this skill?

Accepted Answer

Bolts are rapid iteration cycles (ranging from 2 hours to 3 days) that group related tasks together to ensure a cohesive and fast implementation flow.

Question 5

What is the primary goal of the AI-DLC Mob Elaboration skill?

Accepted Answer

The primary goal is to break down high-level, approved business 'Intents' into granular, actionable 'Tasks' and 'Units' organized in Confluence for team collaboration and architectural validation.

AI-DLC Mob Elaboration

Key Features

Use Cases

AI-DLC Mob Elaboration

Key Features

Use Cases