القائمة
Use when adding or modifying targets in config/targets/ or their overlays in targets/. Do not use for model registry or plugin changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | control-plane-target-registry |
| version | 2026-04-10.1 |
| description | Use when adding or modifying targets in config/targets/ or their overlays in targets/. Do not use for model registry or plugin changes. |
| user-invocable | true |
config/targets/<name>.yaml)targets/<name>/overlay/.agents/skills/targets/<name>/overlay/.opencode/config/targets/ owns target declarations — one file per target.targets/<name>/overlay/ owns the skills and helpers deployed into that repo.root paths must exist on the local machine before the target is valid.bin/aicoder-opencode validate-target <name> after any target config change.config/targets/<name>.yaml and docs/targets/<name>.md for context.bin/aicoder-opencode validate-target <name> — confirm validation passes.bin/aicoder-opencode show-target <name> — confirm fields render correctly.docs/targets/<name>.md with overview, notes, skill chain.| File | Role |
|---|---|
config/targets/<name>.yaml | Target declaration |
targets/<name>/overlay/ | Skills and helpers deployed into the product repo |
docs/targets/<name>.md | Human-readable target overview |
src/cli.ts | Target loading, validation, launcher logic |
config/targets/<name>.yaml created with name, kind, root, default_branch, maintenance_ownerdocs/targets/<name>.md createdtargets/<name>/overlay/.agents/skills/ created with at least one skillbin/aicoder-opencode validate-target <name> passesbin/aicoder-opencode list-targets shows the new targetroot path does not exist locally.agents/skills/ shared baseUse when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.