重构插件入口与runtime安装流程

This commit is contained in:
wxm
2026-05-18 23:52:53 +08:00
parent 373b8601c8
commit d2f34daf16
18 changed files with 274 additions and 87 deletions

View File

@@ -19,10 +19,11 @@ Spawn `creative-director` via Codex custom-agent delegation using gate
**CD-PILLARS** from `references/studio-docs/director-gates.md`.
```
The matching custom agent must already be defined at
`.codex/agents/<agent-name>.toml`. Pass the context listed under that gate's
**Context to pass** field, then handle the verdict using the **Verdict
handling** rules below.
The matching custom agent must already be installed in the target project at
`.codex/agents/<agent-name>.toml`. The plugin source copies for those agents live
in `runtime/agents/`; run `$setup-runtime` if the target project is missing
them. Pass the context listed under that gate's **Context to pass** field, then
handle the verdict using the **Verdict handling** rules below.
Director names are Codex custom agent names. Do not recreate them by pasting
profile text into a generic default agent.
@@ -86,7 +87,7 @@ Apply the resolved mode:
# Apply mode check, then:
Spawn `[agent-name]` via Codex custom-agent delegation:
- Gate: [GATE-ID] (see references/studio-docs/director-gates.md)
- Custom agent file: .codex/agents/[agent-name].toml
- Custom agent file: .codex/agents/[agent-name].toml in the target project
- Context: [fields listed under that gate]
- Codex fork_context: false unless full thread context is required
- Await the verdict before proceeding.
@@ -110,7 +111,7 @@ All gates return one of three verdicts. Skills must handle all three:
| Verdict | Meaning | Default action |
|---------|---------|----------------|
| **APPROVE / READY** | No issues. Proceed. | Continue the workflow |
| **CONCERNS [list]** | Issues present but not blocking. | Surface to user via `ask the user in chat` — options: `Revise flagged items` / `Accept and proceed` / `Discuss further` |
| **CONCERNS [list]** | Issues present but not blocking. | Surface to user via a structured prompt when available, or ask directly in chat: `Revise flagged items` / `Accept and proceed` / `Discuss further` |
| **REJECT / NOT READY [blockers]** | Blocking issues. Do not proceed. | Surface blockers to user. Do not write files or advance stage until resolved. |
**Escalation rule**: When multiple directors are spawned in parallel, apply the
@@ -133,7 +134,7 @@ For phase gates, record in `docs/architecture/architecture.md` or
## Tier 1 — Creative Director Gates
Agent: `creative-director` | Custom agent file: `.codex/agents/creative-director.toml` | Domain: Vision, pillars, player experience
Agent: `creative-director` | Target custom agent file: `.codex/agents/creative-director.toml` | Domain: Vision, pillars, player experience
---
@@ -275,7 +276,7 @@ any session that produces player feedback
## Tier 1 — Technical Director Gates
Agent: `technical-director` | Custom agent file: `.codex/agents/technical-director.toml` | Domain: Architecture, engine risk, performance
Agent: `technical-director` | Target custom agent file: `.codex/agents/technical-director.toml` | Domain: Architecture, engine risk, performance
---
@@ -421,7 +422,7 @@ or before finalizing any engine-specific implementation approach
## Tier 1 — Producer Gates
Agent: `producer` | Custom agent file: `.codex/agents/producer.toml` | Domain: Scope, timeline, dependencies, production risk
Agent: `producer` | Target custom agent file: `.codex/agents/producer.toml` | Domain: Scope, timeline, dependencies, production risk
---
@@ -547,7 +548,7 @@ is invoked
## Tier 1 — Art Director Gates
Agent: `art-director` | Custom agent file: `.codex/agents/art-director.toml` | Domain: Visual identity, art bible, visual production readiness
Agent: `art-director` | Target custom agent file: `.codex/agents/art-director.toml` | Domain: Visual identity, art bible, visual production readiness
---