aidlc-design

Generate domain designs, logical designs, ADRs, and task specifications for approved epics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Bridging the gap between high-level planning and implementation is hard: epics and sprints exist, but teams lack a structured domain model, documented architecture decisions, and implementation-ready task specifications. This Skill guides the AI-DLC Construction Phase by producing Domain Designs, Logical Designs, Architecture Decision Records (ADRs), and validated Task Specifications for approved epics. ## Core Features & Use Cases - Domain and Logical Design: Applies DDD principles (bounded contexts, aggregates, entities, domain events) and layered technical guidance (global, stack-specific, project-level) to propose architecture patterns with deviation analysis against existing codebase patterns. - ADR Generation: Creates Architecture Decision Records for significant decisions, including deviations from organizational standards, with context, consequences, and alternatives. - Task Specification with Quality Gates: Generates implementation-ready task specs with concrete acceptance criteria, data contracts, and error handling, enforced by confidence scoring, detail-sufficiency gates, and publish approval checkpoints. - Multi-Backend Storage: Publishes artifacts to GitLab (markdown files), Linear (design doc issues), or Confluence (child pages) based on automatic backend detection. - Use Case: After running epic decomposition for a new authentication feature, invoke this Skill to model the domain, select architectural patterns, record ADRs, and produce sprint-grouped task specifications ready for team review. ## Quick Start Ask the AI to create the domain model and logical design for your approved epic, for example by saying: create the domain design and ADRs for the authentication epic.

Frequently Asked Questions about aidlc-design

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

FAQPage Schema
How do I create a domain design from an existing epic?

Invoke the skill after epic decomposition is complete and it will gather epic context, analyze existing codebase patterns, and propose a DDD-based domain model with aggregates, entities, and domain events. You validate the model before it proceeds to logical design and ADR creation.

What is an Architecture Decision Record and when are ADRs created?

An ADR documents a significant architectural decision with its context, decision, consequences, and alternatives considered. The skill creates an ADR for each significant design decision, including any deviations from organizational standards or existing codebase patterns.

Does the skill support GitLab, Linear, and Confluence?

Yes, the skill auto-detects the backend from existing feature artifacts. GitLab stores markdown files in design/ and adrs/ directories, Linear creates Design Doc issues, and Confluence stores child pages under the feature document.

What happens if my epic lacks enough detail for design?

The skill runs a confidence assessment scoring epic scope, task quality, detail sufficiency, NFRs, and technical context. Below 60 percent it stops and asks targeted clarifying questions instead of producing a vague design.

Can the design artifacts be published without my approval?

No, the skill enforces hard publish gates. Drafts are shown in chat first, and artifacts are only stored in an In Review state after explicit approval, with a separate final approval gate before task generation proceeds.

When should I use the Quick, Standard, or Deep design gear?

Quick skips design for trivial features, Standard produces a full design document with task specs for a single epic, and Deep runs the complete checklist including domain modeling, ADR sets, and test-scope sub-agents. The gear is carried from the intent phase configuration.