メニュー
Engineering operating model for teams where AI agents generate a large share of implementation output.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when strict TDD is explicitly requested, or when an approved atomic implementation task has already chosen TDD Route strict.
| name | ecc-ai-first-engineering |
| description | Engineering operating model for teams where AI agents generate a large share of implementation output. |
| origin | ECC |
Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.
Prefer architectures that are agent-friendly:
Avoid implicit behavior spread across hidden conventions.
Review for:
Minimize time spent on style issues already covered by automation.
Strong AI-first engineers:
Raise testing bar for generated code:
