aidlc-setup

Automate AI-DLC environment setup by generating .aidlc/config.toml and configuring tools.

24|2|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill aidlc-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-setup
Source: https://github.com/ikeisuke/ai-dlc-starter-kit/tree/main/skills/aidlc-setup
Command: npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill aidlc-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, gh, dasel, jq, python3, perl, git, awk, sed, and includes scripts (resource) components.

What problem does it solve?

AI-DLC environment setup for new projects is streamlined by automatically detecting the project root, generating the .aidlc/config.toml, and configuring AI tools to reduce manual configuration time.

Core Features & Use Cases

  • Detects project root and determines whether setup is needed, migrated, or upgrading is required.
  • Generates or migrates .aidlc/config.toml and scaffolds necessary directories and templates for AI-DLC workflows.
  • Configures AI tooling (Claude Code) and provides templates to accelerate onboarding for new projects.

Quick Start

Run /aidlc-setup from your project root to start the automated environment provisioning.

Frequently Asked Questions about aidlc-setup

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

FAQPage Schema
How do I automate AI-DLC environment setup for a new project?

To automate AI-DLC environment setup, run the setup command from your project root to automatically detect the directory, generate the .aidlc/config.toml file, and configure AI tools like Claude Code for immediate workflow use.

What is the process for migrating an existing AI-DLC config to a new version?

Migrating an AI-DLC config to a new version requires detecting the current setup state and upgrading the configuration. The automated process handles v1 to v2 migrations and file migrations to ensure existing projects transition smoothly without manual config rewriting.

Do I need specific command-line utilities installed to use an automated AI-DLC setup?

Automated AI-DLC setup requires bash and a set of utilities including gh, dasel, jq, python3, perl, git, awk, and sed. These tools are essential for the script to perform environment discovery, file migration, and AI tool configuration.

How does automated project root detection work for AI-DLC workflows?

Automated project root detection for AI-DLC workflows uses bash and utilities like git to scan the directory. It determines the root path to decide whether a new setup is needed, a migration is required, or an upgrade is necessary.

Can I use this automated setup to scaffold directories and templates for Claude Code?

Yes, you can use this automated setup to scaffold directories and templates for Claude Code. The process generates the .aidlc/config.toml file and configures the AI tooling directly, accelerating onboarding for new AI-DLC projects.

What are the limitations of using bash scripts for AI-DLC environment configuration?

Using bash scripts for AI-DLC environment configuration limits execution to environments supporting bash and its required utilities like dasel, jq, and perl. The setup will fail if any of these specific command-line dependencies are missing from the system path.