メニュー
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.
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 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.
AI-DLC workflow orchestrator. Start, resume, or manage an AI-driven development lifecycle. Scopes are defined one file per scope under `.claude/scopes/`; run `bun .claude/tools/aidlc-utility.ts help` for the authoritative list and descriptions. Utilities: --status, --doctor, --stage, --phase, --scope, --depth, --test-strategy, --version, --help, plus the intent and space verbs. Or describe what you want to build and the scope will be auto-detected.
| name | aidlc-bugfix |
| description | 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. |
| argument-hint | [description | --status | --stage <slug|#> | --phase <name|#>] |
| user-invocable | true |
Drive the AI-DLC engine with the bugfix scope fixed. This is the same
deterministic forwarding loop the /aidlc orchestrator runs, with --scope bugfix baked into the first next so scope detection is skipped. The
engine owns all routing; the conductor persona arrives on the first directive's
conductor_persona field — adopt it for the whole run.
directive = bun .claude/tools/aidlc-orchestrate.ts next --scope bugfix $ARGUMENTSdirective.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see aidlc-common/protocols/stage-protocol.md.bun .claude/tools/aidlc-orchestrate.ts report --stage <directive.stage> --result <outcome> [--user-input "<text>"] when the directive names a stage; omit --stage only for non-stage report round-trips.directive.kind == done.Pass $ARGUMENTS through verbatim after --scope bugfix; the engine parses
any flags (--status, --stage, …) and the --scope from the
state file always wins on an existing workflow, so re-running a started workflow
resumes it. To run a different scope, use /aidlc --scope <other> instead.