Verified:GitHub

aidlc-init

Configure AI-DLC project settings for Jira, Confluence, GitLab, and Linear into aidlc.config.yaml.

Updated Jul 22, 2026

Search Tags:#project setup #configuration #linear #jira #gitlab #confluence #ai-dlc

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill aidlc-init-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: aidlc-init
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/aidlc/skills/aidlc-init
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill aidlc-init-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-DLC workflows need organisation-specific connection details (Jira project keys, Confluence spaces, GitLab doc repos, Linear teams), and hardcoding them into every skill causes errors and maintenance overhead. This Skill collects those settings once and writes them to a single aidlc.config.yaml file that all other AI-DLC skills read. ## Core Features & Use Cases - Centralized Configuration: Captures Atlassian cloud ID, Confluence space key, Jira project key and issue types, GitLab docs repo URLs, and Linear team key into one YAML file. - Backend Selection: Lets you choose GitLab, Linear, or Confluence as the default documentation backend and only prompts for relevant sections. - Optional Project Constitution: Offers to generate a one-page aidlc.constitution.md of project principles and constraints that intent, design, and verify phases check against. - Use Case: When onboarding a repository to AI-DLC for the first time, run this once to record your Jira project key and GitLab docs repo, then proceed to /aidlc-intent without re-entering organisation details. ## Quick Start Ask the assistant to initialize AI-DLC configuration for this project and answer the prompts for your Jira, Confluence, GitLab, or Linear settings.

Frequently Asked Questions about aidlc-init

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

FAQPage Schema

How do I set up AI-DLC configuration for a new project?▼

Run /aidlc-init once per project before any other AI-DLC skill. It prompts for your documentation backend (GitLab, Linear, or Confluence), collects the relevant connection details, and writes them to aidlc.config.yaml in the project root.

What settings does aidlc.config.yaml contain?▼

The file stores the default backend, Atlassian cloud ID, Confluence space key, Jira project key and issue types, GitLab docs repo URLs, Linear team key, and optional work item template settings. Other AI-DLC skills resolve placeholder tokens from these values.

Can I use AI-DLC with Azure DevOps instead of Jira?▼

Yes, the configuration supports Azure DevOps through the ado section with its own project name and issue types (Epic, User Story, Task). ADO nests Task under User Story natively, so leafAttach is set to parent.

Why do other AI-DLC skills report unresolved placeholder tokens?▼

Placeholders like <CONFLUENCE_SPACE_KEY> remain unresolved when aidlc.config.yaml is missing or the corresponding value is blank. Run /aidlc-init to create or update the config, then retry the skill that reported the error.

Should aidlc.config.yaml be committed to git?▼

The file may contain internal URLs and keys, so the skill warns you and offers to add it to .gitignore if those values are sensitive. Non-sensitive configurations can be committed to share settings across the team.