菜单
Install or update the AI-DLC v2 framework (AI-Driven Development Lifecycle, from awslabs/aidlc-workflows) in the current project, then hand off to the installed /aidlc workflow. Run this once per project, and again after upgrading the plugin. Pass --check to preview changes without writing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Drive an AI-DLC v2 plugin release — sync an upstream release-tag snapshot, review the diff, set the mirrored version, build, run the verification gates, commit and tag locally, and write a summary report. Stops before pushing/publishing.
Run the AI-DLC workflow with the bugfix scope baked in — no scope detection. Fix a specific bug. Packaging over `/aidlc --scope bugfix`, which works without this skill.
Run the AI-DLC workflow with the feature scope baked in — no scope detection. Default for new features, practical depth. Packaging over `/aidlc --scope feature`, which works without this skill.
Start an AI-DLC workflow — run the whole Initialization phase (mint the intent, detect the workspace, build state) in one step, without typing a stage. The engine normally auto-births the first intent; this is opt-in packaging over that move. Pass `--scope <name>` to seed the initial scope (defaults to poc), or a freeform description of what to build.
Run the AI-DLC workflow with the mvp scope baked in — no scope detection. Skip operations, ship the core. Packaging over `/aidlc --scope mvp`, which works without this skill.
Run the AI-DLC workflow with the security-patch scope baked in — no scope detection. CVE response. Packaging over `/aidlc --scope security-patch`, which works without this skill.
| name | aidlc |
| description | Install or update the AI-DLC v2 framework (AI-Driven Development Lifecycle, from awslabs/aidlc-workflows) in the current project, then hand off to the installed /aidlc workflow. Run this once per project, and again after upgrading the plugin. Pass --check to preview changes without writing. |
| argument-hint | [--check] |
This plugin ships upstream's Claude Code framework tree verbatim and installs it
into the current project (the engine requires living at <project>/.claude/ —
its hooks and tools resolve paths under the project root). After installation,
every upstream command works exactly as documented: /aidlc, /aidlc-<stage>,
/aidlc --doctor, etc.
Follow these steps exactly. Do not improvise around a failed step.
Run bun --version. If it fails, STOP and tell the user: AI-DLC's tools and
hooks are TypeScript run via bun. Install it with
curl -fsSL https://bun.sh/install | bash (Windows: npm install -g bun), make
sure bun is on the PATH of non-interactive shells (~/.zshenv for zsh,
~/.bashrc for bash), then re-run this skill.
From the project root, run:
bun "${CLAUDE_PLUGIN_ROOT}/installer/aidlc-install.ts" $ARGUMENTS
The installer is idempotent and never overwrites user data silently: on a
FRESH install, any existing file that differs from the framework's is a
CONFLICT (left untouched and reported, exit code 3); on an UPDATE of an
existing install, framework files are refreshed and every differing overwrite
is listed. settings.json is additively merged (nothing the user wrote is
changed), .mcp.json only gains missing servers, .gitignore only gains the
AI-DLC block, the aidlc/ workspace is seeded only where files are absent,
.claude/settings.local.json is never touched, and it refuses to write
through symlinks. --check previews without writing.
Show the installer's report verbatim, then follow ITS guidance:
/aidlc with a description of what to build./aidlc (the
installed orchestrator — not this plugin skill).If the installer fails, show its error verbatim and stop — do not hand-edit the
project's .claude/ to work around it.