菜单
Clarify and scope incoming product or engineering requests before research, architecture, or coding starts. Use when the request is broad, emotionally urgent, ambiguous, risky, multi-phase, missing success criteria, missing constraints, missing non-goals, or likely to create rework if the agent starts implementation too early.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit any product surface against accessibility standards: WCAG 2.2 AA for web, Apple UIKit/SwiftUI Accessibility for iOS, Android TalkBack/AccessibilityService for Android, Microsoft UIA for Windows, AT-SPI for Linux, game-specific readability and remappable-controls patterns, and voice/chat AI surfaces with appropriate alternative modes. Produces a per-criterion status, automated test suggestions, manual test scripts, screen-reader transcripts, contrast measurements, and a release-gate verdict that names the fixed and outstanding findings. Use after ux-design and before release on every surface with user interaction.
Design or review the operational harness around single-agent, multi-agent, and tool-using AI systems. Use when building agent platforms, routing layers, tool interfaces, memory systems, evaluation harnesses, human checkpoints, permission boundaries, cost controls, or agent-computer interfaces that must remain observable, testable, and safe under real project work.
Run an AI-augmented Product Development Lifecycle that treats every phase as a hypothesis to test, not a deliverable to push: research, hypothesis, plan-by-phases, prototype, validate, implement under TDD, harden against the matching security track (OWASP/MASVS) and CVE risk, and ship with rollback and post-launch evaluation. Use as the strategic spine when a project is greenfield, a brownfield refactor, an experiment, or a feature whose value is not yet proven; cooperates with sdlc-orchestrator (operational chain) and hypothesis-validator (evidence).
Analyze an existing repository in read-only mode to reconstruct current behavior, architecture, dependency clusters, build and test health, hotspots, tech debt, ownership boundaries, integration points, and current-vs-target gaps. Use for existing-product improvement, migration planning, code archaeology, risky refactors, unfamiliar repositories, or artifacts `80-current-state-scan.md` through `85-migration-plan.md` before writing code.
Design or review software architecture using system context, container, component, runtime, deployment, data, API, integration, crosscutting concepts, and ADR artifacts. Use before large implementation, service-boundary changes, infrastructure changes, API or data contract changes, migrations, reliability work, security-sensitive design, or architecture artifacts `14-system-context.md` through `22-adr-index.md`.
Use for CI/CD, pipeline automation, GitHub Actions, GitLab CI, Jenkins, Argo, Azure DevOps, build-test-scan-package-deploy flows, release orchestration, protected environments, approvals, and rollback.
| name | intake-coordinator |
| description | Clarify and scope incoming product or engineering requests before research, architecture, or coding starts. Use when the request is broad, emotionally urgent, ambiguous, risky, multi-phase, missing success criteria, missing constraints, missing non-goals, or likely to create rework if the agent starts implementation too early. |
Turn an unclear request into a working brief without making the user repeat themselves. Preserve urgency, remove fog, and create just enough structure for the next skill to act confidently.
../../routing/principal-operating-model.md before moving from analysis to implementation.Hand off a concise brief plus the exact uncertainties the next skill must resolve.
references/brief-template.md: Use this template for 01-request-brief.md and 02-clarifications.md.