菜单
Use when the user writes /zno-deploy or asks about deployment, release, environments, migration, or rollback. Plans and executes the deployment change, updates docs/operations/08-deployment.md, and updates local-development docs when commands or env vars change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | zno-deploy |
| description | Use when the user writes /zno-deploy or asks about deployment, release, environments, migration, or rollback. Plans and executes the deployment change, updates docs/operations/08-deployment.md, and updates local-development docs when commands or env vars change. |
<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).
Restate the deployment change: target environment, what is being released or migrated, and the expected outcome.
Clarify only what affects environments, data migration, secrets handling, downtime, or rollback strategy.
If the deployment involves choosing a platform, CI/CD, containerization, or monitoring stack, apply the technical selection gate from references/tech-gate.md first.
Plan the change across: build, environment config, migration steps, verification steps, and rollback path. Never deploy to production without an explicit user go-ahead.
Update docs/operations/08-deployment.md before or alongside the change. If it does not exist yet, scaffold it first:
python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold deploy
If local commands or environment variables changed, also update docs/operations/07-local-development.md (--scaffold local-dev if missing).
Verify the deployment: health checks, smoke tests, or the project's verification commands. Report results factually per references/verification.md.
Record the release in docs/development/03-feature-changelog.md when it ships user-visible behavior.
<skills-root>/zno-init/references/docs-map.md — full doc set, doc update rules, scaffold triggers.<skills-root>/zno-init/references/tech-gate.md — technical selection gate and performance-aware design.<skills-root>/zno-init/references/verification.md — verification gate and final-response page test steps.Use when the user writes /zno-change or asks to change existing behavior or scope in an ongoing project. Identifies the affected docs and code before implementing, updates them together with the change, and records the change in the feature changelog.
Use when the user writes /zno-continue or starts a new session wanting to resume where a previous conversation left off. Reads the status snapshot and supporting docs, summarizes the project state, then continues with the next safe task.
Use when the user writes /zno-evaluate or wants to validate whether a project idea is worth doing before committing. Uses Socratic questioning to challenge the idea across pain points, target users, existing solutions, ROI, risks, and timeline. Outputs a structured evaluation conclusion (do / don't do / defer). Should be used before /zno-init.
Use when the user writes /zno-feature or asks to add a new feature to an ongoing project. Clarifies only what affects scope or design, follows TDD when a test framework exists, updates the relevant docs and the feature changelog, and passes the verification gate before completion.
Use when the user writes /zno-fix or reports a bug or defect. Reproduces or reasons about the defect, locates the root cause, fixes it with a regression test when possible, verifies the fix, and updates the changelog if behavior changed.
Use when the user writes /zno-goal (optionally with --super), gives a whole project or phase objective, or says they don't want to issue per-feature commands. Executes the document-first workflow autonomously through phases and tasks, stopping only at required confirmation gates. With --super, ordinary confirmations are skipped and decisions are logged instead.