メニュー
Shared return contract for SGAI Task subagents. Use before any delegated implementation, deployment, writing, verification, review, or project-critic subagent reports back to its caller.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Go code review checklist based on official Go style guides. When reviewing Go code for style, idioms, and best practices
Guide for creating custom opencode agents with proper configuration, permissions, path-based delegation, work splitting, and strict status envelopes. Use when creating or updating agents for coordination, implementation, review, deployment, verification, documentation, or specialized workflows.
TDD for process documentation - test with subagents before writing, iterate until bulletproof. When you discover a technique, pattern, or tool worth documenting for reuse. When editing existing skills. When asked to modify skill documentation. When you've written a skill and need to verify it works before deploying. When skills fail to help agents, when documentation is unclear, when new patterns emerge that need standardization.
Create and setup a new OpenAI Agents SDK application with interactive guidance for language choice, agent type selection (Basic, Voice, Realtime), project setup, and automatic verification.
Create and setup a new Claude Agent SDK application with interactive guidance for language choice, project setup, and automatic verification.
Problem-Solving Dispatch; Dispatch to the right problem-solving technique based on how you're stuck; Stuck on a problem. Conventional approaches not working. Need to pick the right problem-solving technique. Not sure which skill applies.
| name | subagent-return-protocol |
| description | Shared return contract for SGAI Task subagents. Use before any delegated implementation, deployment, writing, verification, review, or project-critic subagent reports back to its caller. |
Use this skill when a Task subagent reports completion, concerns, missing context, review findings, or blockers to the agent that invoked it.
TASK_PACKET paths first when a packet is provided.NEEDS_CONTEXT.NEXT_OWNER: invoking agent when the caller should reconcile the result.NEXT_OWNER: coordinator only when the coordinator must decide or route the next step.project-critic only when your prompt names that wrapper as the caller.Use this for implementation, deployment, writing, cleanup, and other work-producing subagents:
STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
TASK: ...
READ_PATHS:
- ...
CHANGED_PATHS:
- ...
VERIFICATION:
- command: ...
result: ...
EVIDENCE:
- ...
REVIEW_SCOPE:
- ...
CONCERNS:
- ...
NEXT_OWNER: invoking agent | coordinator
Use this for reviewer, verifier, safety-review, and project-critic subagents:
REVIEW_STATUS: PASS | NEEDS_WORK | NEEDS_CONTEXT | BLOCKED
SCOPE_REVIEWED:
- ...
EVIDENCE_REVIEWED:
- ...
FINDINGS:
- file:line - required fix
BLOCKERS:
- ...
NEXT_OWNER: invoking agent | developer | coordinator
DONE: completed the task with required verification.DONE_WITH_CONCERNS: completed the task, but caller must consider listed concerns.PASS: reviewed scope has no required fixes.NEEDS_WORK: caller must route listed findings for fixes.NEEDS_CONTEXT: caller must provide only the missing context listed.BLOCKED: caller must resolve the blocker before this work can complete.FINDINGS, not prose outside the envelope.BLOCKERS.NEXT_OWNER about routing, not blame.