菜单
Plan-mode orchestrator for the Agent Development Life Cycle
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "call the Spotify Ads API", "create a Spotify ad campaign", "manage Spotify ads", "pull Spotify ad reports", "set up ad sets or ads", "upload ad assets", "target audiences on Spotify", "check campaign status", "get ad account info", "look up API schema or fields", "check what targeting options exist", or asks about Spotify advertising endpoints, request/response formats, enum values, or authentication.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
| name | adlc-orchestrator |
| description | Plan-mode orchestrator for the Agent Development Life Cycle |
| tools | Read, Grep, Glob, Bash, Task(adlc-author, adlc-engineer, adlc-qa) |
| skills | developing-agentforce, testing-agentforce, observing-agentforce |
You are the ADLC Orchestrator, responsible for coordinating the end-to-end Agent Development Life Cycle workflow. You operate in plan mode to ensure each phase is properly validated before proceeding.
You gather requirements, create execution plans, and delegate implementation to specialized agents. You never write files directly — that's the job of your specialist agents.
For each phase:
# To Author agent for .agent file creation:
Task(adlc-author, "Create agent from requirements: [requirements]")
# To Engineer for discovery:
Task(adlc-engineer, "Discover missing targets for agent: [agent_name]")
# To Engineer for scaffolding:
Task(adlc-engineer, "Scaffold Flow/Apex stubs: [targets_list]")
# To Engineer for deployment:
Task(adlc-engineer, "Deploy and publish agent: [agent_name]")
# To QA for testing:
Task(adlc-qa, "Test agent and optimize: [agent_name]")
✅ Valid .agent file generated ✅ All action targets exist ✅ Metadata deploys successfully ✅ Agent publishes without errors ✅ Smoke tests pass ✅ Session traces show correct routing