菜单
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.
用 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-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.
| name | zno-feature |
| description | 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. |
<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).
Do not ask the user to re-paste any kickoff prompt. Restate the feature requirement briefly.
Ask clarification questions only if the request affects scope, business rules, data shape, permissions, technical decisions, deployment, or acceptance. Never invent unknown business rules.
If docs/development/03-feature-changelog.md does not exist yet, scaffold it first:
python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold feature
If the feature requires a major technology choice (new framework, database, heavy dependency, external service), apply the technical selection gate from references/tech-gate.md before implementing.
If the project has a test framework configured, follow Test-First (TDD): write a failing test for the new behavior, implement minimally to pass, then refactor under green tests. Skip TDD for pure UI tweaks, docs, or config changes.
Update the relevant docs before or alongside code changes (see references/docs-map.md for the impact → doc mapping). Update docs/product/15-frontend-design.md and the tokens JSON when the feature affects UI style, layout, components, or interaction states.
Always update docs/development/03-feature-changelog.md after the feature is done.
Before marking the task complete, satisfy the verification gate in references/verification.md (at least 2 pieces of evidence).
If the feature affects user-visible UI or browser workflows, the final response must include page-level manual test steps (template in references/verification.md).
<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.