菜单
Convert approved Neo context and design into thin vertical implementation slices with focused verifiers, compatibility, rollout, rollback, and replan conditions. Use only with a delivery-stage handoff generated by $neo. Do not use directly, create horizontal layer batches, or implement the slices.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Restate the immediately preceding assistant response in plain, concise human language without jargon while preserving important details and useful formatting. Use when the user says "bro", asks for a simpler explanation, or wants a technical answer made easier to read.
Independently review a candidate software change against its original plan, repository constraints, behavior, tests, design quality, compatibility, security, operations, and verification evidence without modifying files. Use for review-only requests, fresh-context $ship review handoffs, or evidence-led diff assessment. Do not use to implement fixes, refactor code, resolve existing GitHub review threads, perform product or architecture design, or approve a change whose governing plan is missing.
Deploy one release-ready immutable software candidate through the repository's established deployment path, observe declared health signals, and stop, roll back, or hand off forward repair when rollout conditions fail. Use only when the user explicitly invokes $deploy with a target environment and deployment authority. Do not use for implementation, release-readiness review, CI-only verification, implicit production mutation, or a candidate lacking identity, recovery, and health evidence.
Inspect and control live Hunk diff-review sessions through the non-interactive `hunk session` CLI. Use when the user has Hunk running, wants an interactive diff walkthrough, or wants inline Hunk comments. The daemon uses localhost, so sandboxed agents must request network or sandbox access before discovering sessions.
Resolve system boundaries, contracts, data and control flow, quality scenarios, failure behavior, and architectural tradeoffs for an active Neo task. Use only with an architecture-stage handoff generated by $neo. Do not use directly, reduce architecture to technology selection, or implement code.
Resolve system boundaries, contracts, data and control flow, quality scenarios, failure behavior, and architectural tradeoffs for an active Neo task. Use only with an architecture-stage handoff generated by $neo. Do not use directly, reduce architecture to technology selection, or implement code.
| name | neo-delivery |
| description | Convert approved Neo context and design into thin vertical implementation slices with focused verifiers, compatibility, rollout, rollback, and replan conditions. Use only with a delivery-stage handoff generated by $neo. Do not use directly, create horizontal layer batches, or implement the slices. |
Work only on the active Neo delivery stage.
Use the <neo-cli> already resolved by the active $neo router. If it is not
present in the handoff context, resolve
scripts/neo.py from the installed neo skill's
source location.
neo.py handoff <slug> --expect delivery..neo/tasks/<slug>/delivery.md and gate it with
neo.py gate <slug> --stage delivery --artifact <path>.If no user input is required, return control to $neo to continue finalization
in this context. Do not implement a slice.