菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Zedi 固有の Cloudflare 作業ガイド。Railway → Cloudflare 移行（Issue #1088）で Terraform を全廃し、Wrangler（wrangler.jsonc）と Cloudflare MCP を正本にする際の 使い分け・命名・トークンスコープ・フェーズ計画をまとめる。 Use when working on Cloudflare for Zedi: migrating server/api, server/mcp, server/hocuspocus, Postgres/Redis/S3 to Workers/D1/KV/R2/Durable Objects, moving frontend/admin from Pages to Workers Static Assets, removing Terraform, or reconfiguring CI/CD. Triggers: "Cloudflare 移行", "Workers 化", "R2", "D1", "Durable Objects", "Terraform 廃止", "wrangler", "#1088"〜"#1095".
Run the AI-DLC `application-design` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage application-design --single`: the engine emits one run-stage directive for application-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.
Run the AI-DLC `approval-handoff` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage approval-handoff --single`: the engine emits one run-stage directive for approval-handoff and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.
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 `build-and-test` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage build-and-test --single`: the engine emits one run-stage directive for build-and-test and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.
Run the AI-DLC `ci-pipeline` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage ci-pipeline --single`: the engine emits one run-stage directive for ci-pipeline and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.
| name | aidlc-security-patch |
| generated-by | aidlc-runner-gen |
| description | 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. |
| argument-hint | [description | --status | --stage <slug|#> | --phase <name|#>] |
| user-invocable | true |
Drive the AI-DLC engine with the security-patch scope fixed. This is the same
deterministic forwarding loop the /aidlc orchestrator runs, with --scope security-patch 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 .codex/tools/aidlc-orchestrate.ts next --scope security-patch $ARGUMENTSdirective.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see aidlc-common/protocols/stage-protocol.md.bun .codex/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 security-patch; 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.