Menú
Standard procedure when you operate as the coder role: the end-to-end workflow, output conventions, and memory-protocol rules to follow before any tool call.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Standard procedure when you operate as the reviewer role: end-to-end pre-delivery artifact survey, severity-tiered findings, and report format that goes with the role's identity.
Standard procedure when you operate as the webSearcher role: end-to-end web-retrieval workflow, output conventions, and memory-protocol rules to follow before any fetch.
The main orchestrator's standing delivery procedure: triage, then for real work open a goal root, decompose into a stage graph, dispatch in waves, settle each result, review, deliver, and close the root.
Workflow and judgment layer for the cluster job tool — the whole job lifecycle (launch, monitor, wrap up), the decisions and parameter choices at each stage, output conventions, and the blockers you escalate. Operations: capacity, submit, list, get, logs, events, stop, delete.
Standard procedure when you operate as the localExplorer role: end-to-end read-only local lookup workflow, output conventions, and memory-protocol rules.
Capture a repeatable method — the how of a multi-step workflow — as a new skill. For one-off facts or preferences use `remember` instead.
| name | coding-workflow |
| description | Standard procedure when you operate as the coder role: the end-to-end workflow, output conventions, and memory-protocol rules to follow before any tool call. |
| when_to_use | Use as your first action when dispatched as the coder role — the body holds the full workflow you should follow. The coder role prompt is intentionally identity-only and depends on this skill for procedure. |
| allowed-tools | ["Read","Write","Edit","Grep","Glob","Bash","TodoWrite","MemoryRead","MemoryWrite"] |
| roles | ["coder"] |
Procedure for taking a coding request from understanding to verified delivery.
pnpm typecheck", "this repo uses pnpm + tsdown", "test fixture lives at X/Y/Z") that saves discovery. But memory is a hint, not a fact — see #3.pnpm typecheck", a quick probe (pnpm typecheck --help or running it) confirms before you depend on it. Memory shortens the lookup path; it does not skip verification.Files changed: list with one line per file (path + one-phrase what), then a Verification: block with the commands you ran and their outcomes.pnpm tc but it's now pnpm typecheck").