菜单
Use when the user writes /zno-status, wants to save current progress before switching or ending a session, or asks for a progress snapshot. Inspects the workspace and writes a factual, handoff-ready snapshot to docs/development/10-current-status.md. Does not implement new work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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-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.
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.
| name | zno-status |
| description | Use when the user writes /zno-status, wants to save current progress before switching or ending a session, or asks for a progress snapshot. Inspects the workspace and writes a factual, handoff-ready snapshot to docs/development/10-current-status.md. Does not implement new work. |
<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).
Inspect the current state: relevant docs, and git status / recently changed files when available.
If docs/development/10-current-status.md does not exist yet, scaffold it first:
python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold status
Record in the status doc: current phase, current task, completed work, in-progress work, pending next steps, blockers, recent file changes, what verification ran, what verification did NOT run, and continuation advice.
Keep the snapshot strictly factual. Never claim tests ran unless they actually ran.
Do not implement new work unless the user explicitly asks.
Final response: confirm the snapshot was updated and state the recommended next step (usually /zno-continue in the next session).
<skills-root>/zno-init/references/docs-map.md — full doc set, doc update rules, scaffold triggers.