Bootstrap DevOpsFlow Codex hook runtime assets into an installed plugin mirror before other hooks run.
使用事件风暴、CQRS 和需求追踪进行通用 DDD 领域建模。Use this skill when Codex needs to clarify raw business requirements, split stakeholder needs into requirement items, evolve a persistent domain model, identify actors and multi-role collaboration, domain events, commands, policies, aggregates, domain services, read models, produce structured Markdown or optional Mermaid/PlantUML diagrams, and review designs that may be CRUD, database, package-structure, or DDD-terminology driven instead of problem-domain driven. Especially use for CRUD-looking admin requirements such as company, department, position, employee, account, role, or permission management that need behavior-first modeling instead of flat noun aggregates.
Design and review strict Google Cloud IAM-style authorization catalogs for RBAC and ABAC across REST, GraphQL, gRPC, protobuf, and mixed API surfaces. Use when Codex needs to name permissions or roles, define role bindings and CEL conditions, map API operations to authorization checks, migrate legacy colon-delimited permissions, or prevent multiple authorization naming schemes.
Pure TDD workflow for greenfield feature development, bug fixes, behavior-preserving refactors, characterization tests, and characterize-then-fix work. Use when Codex needs test-first discipline to build new behavior from scratch or change existing code without drifting behavior. Applies across languages and architectures. Do not use for technology-specific layering rules, documentation-only edits, trivial formatting-only changes, or purely exploratory prototypes where no executable behavior is expected.
Design, review, and refactor resource-oriented HTTP, REST, gRPC transcoding, protobuf, and OpenAPI APIs using Google API Improvement Proposals (AIP). Use when Codex needs to create or critique API endpoints, REST URI version prefixes, resource names, standard methods, custom methods, pagination, filtering, field masks, errors, long-running operations, protobuf service definitions, or api-linter setup against Google AIP guidance.
Mandatory engineering workflow router. Use at the start of software development, refactoring, bug fixing, domain modeling, glue coding, API or authorization design, code review, verification, branch finishing, or commit preparation to classify the task and select required skills such as df-resumable-workflow-guard, df-ddd-event-storming-design, df-glue-coding, df-iam-access-control-design, df-ddd-to-tdd-handoff, df-implementation-planning, df-executing-implementation-plan, df-tdd-skill, df-spring-web-boundaries, df-systematic-debugging, df-requesting-code-review, df-receiving-code-review, df-verification-before-completion, df-finishing-development-branch, or df-parallel-agent-orchestration.
Glue Coding workflow for AI implementation that should reuse local project material without blindly copying old structure. Use after domain ambiguity has been resolved or declared thin, and before implementation planning or coding, when a task resembles existing CRUD pages, list/form/detail screens, imports/exports, endpoints, adapters, command handlers, projections, tests, configuration, refactors, migrations, modernization, or other repeatable project patterns. The skill discovers local style packs, reference code, examples, docs, AGENTS.md rules, and nearby production implementations, classifies them as target patterns, legacy patterns, anti-patterns, or behavior evidence, preserves the right conventions, and limits new code to the intended delta.
Protect long-running or interruption-prone engineering work with explicit checkpoints, resume files, and handoff notes. Use when a task may span multiple turns or sessions, exceed about 30 minutes, touch multiple workflow stages, require repeated verification, approach context limits, resume after interruption/compaction, or when the user says continue, resume, checkpoint, long task, handoff, 中断, 继续, 续跑, 检查点, 长任务, or 交接.