nano-core-coder-ops

name	nano-core-coder-ops
description	Operate nano-core coding delegation. Use for /coder or /coding execution, /coder-plan or /coder_plan planning, natural-language coding approval prompts, delegated runs, run IDs, progress, cancellation, and final-result handling; not for direct coding or automatic delegation.

nano-core Coder Operations

Follow the current delegation policy. Read {baseDir}/references/safety.md before starting or diagnosing a delegated coding run.

When to use this skill

• Use for explicit coding delegation commands, plan/execute approval controls, delegated run status, or duplicate-result behavior.
• Use when explaining why a natural-language coding request stayed in the main assistant or prompted for approval.

When not to use this skill

• Do not use for direct coding work that is not being delegated.
• Do not silently convert natural-language coding requests into delegated execution.
• Do not delegate from non-main chats, scheduled tasks, evaluators, or maintenance runs.

Delegation behavior

• /coder <task> and /coding <task> explicitly request delegated execution.
• /coder-plan <task> and /coder_plan <task> explicitly request read-only delegated planning.
• Substantial natural-language coding requests may produce Plan, Execute, or Cancel approval controls; they do not automatically start the coding worker.
• Execute mode runs directly against the group's own workspace directory (mounted at /workspace/group) using mutating tools; it does not use a separate isolated worktree. Plan mode uses read-only tools and makes no changes.
• The outer assistant delegates exactly once for an approved request and returns the delegated outcome without duplicating a streamed final response.

Operational checks

1. Confirm the request originated in main/admin chat and is not scheduled, evaluator, maintenance, or bootstrap-gated work.
2. Confirm the requested mode: plan or execute.
3. Preserve and surface the delegated run ID (coder-<timestamp>-<suffix>).
4. Report progress without claiming completion before the worker's terminal result.
5. On execute mode, report changed files from the group workspace (e.g. git status/git diff in groups/<group>/) and the verification commands that were run.
6. On cancellation or failure, preserve the group workspace state and report what is recoverable.

Guardrails

• Never run destructive git commands unless explicitly requested.
• Preserve unrelated worktree changes.
• Coding delegation is main/admin chat only.
• Do not bypass the approval gate or fabricate delegated progress, changes, tests, commits, or pull requests.