القائمة
Implement one task on a feature branch. Use when: the Planner has dispatched a `task_assignment` to the Coder role; reading existing code; producing a diff; running a local build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Validate and fact-check another agent's output against evidence and the task's success criteria. Use when: verifying a report, fact-checking claims, cross-checking research findings, confirming a result meets its criteria. Not for browser/E2E testing (see e2e-runner).
Procedure the Researcher agent follows to answer a question with web search + page fetch: plan queries, search, open the promising pages, cross-check, and return a source-cited synthesis. Use when a task needs current or external facts.
Example skill scaffold. Replace this with a real, project-specific procedural playbook. The description must clearly state WHEN to use the skill (trigger phrases and scope) so the model can match it to user intent. USE FOR: <list the situations this skill applies to>. DO NOT USE FOR: <list out-of-scope situations and point to the right skill>.
The Planner's operating procedure. Use when: turning a principal goal into a Plan; revising a plan after rejection; dispatching ratified tasks; supervising sub-agent results; deciding whether to convene the Council; finalizing a run.
Classify a proposed action's risk tier (T0–T4), apply the gate policy, and (if required) summarize the proposal into a human-reviewable approval request. Use whenever an agent is about to perform an action that touches anything outside its own scratch state.
Append a structured event to the run's provenance log. Every agent calls this for every meaningful state transition (plan drafted, task dispatched, action proposed/executed, approval decided, etc.) so the run is fully replayable and auditable.
| name | coder-runner |
| description | Implement one task on a feature branch. Use when: the Planner has dispatched a `task_assignment` to the Coder role; reading existing code; producing a diff; running a local build. |
| argument-hint | Path to the task_assignment message, e.g. runs/<runId>/messages/<msg>.json |
task_assignment for role coder lands in runs/<runId>/messages/.coder.agent.md.shared/approval-gate/SKILL.md and
shared/provenance/SKILL.md.shared/schemas/task.schema.json and
task-result.schema.json.task_assignment message. Confirm:
assigneeRole === "coder".requiredCapabilities ⊆ your_grant. If not, return blocked_on_dependency.riskTier ≤ T2. T3/T4 work belongs to Ops; refuse and surface.task_started to provenance.feat/<runId>-<task-slug>. All writes go
here. No edits to main, release/*, e2e-agent/e2e-test/test-definitions/**, or any path
outside the repo's source tree.run:build. Capture the build log under
runs/<runId>/artifacts/<task-id>/build.log.run:tests, that is fine — the QA agent will pick it up downstream.runs/<runId>/artifacts/<task-id>/diff.patch.TaskResult. status: success if criteria met; partial with explicit
gaps if not; failure if the work cannot be completed within the grant.task_result to provenance and send the message to the Planner.Any action above T2 (push to main, deploy, mass file deletion, etc.) is not your job.
Emit an ActionProposal describing what should be done, return
status: blocked_on_approval, and let the Planner reassign.
🚧 Scaffold — runner is documented; implementation TBD.