メニュー
Use when the user writes /zno-roadmap or wants to adjust project phases, priorities, MVP boundary, or milestones. Updates docs/product/06-roadmap.md and keeps it consistent with the current status and changelog.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | zno-roadmap |
| description | Use when the user writes /zno-roadmap or wants to adjust project phases, priorities, MVP boundary, or milestones. Updates docs/product/06-roadmap.md and keeps it consistent with the current status and changelog. |
<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).
docs/product/06-roadmap.md, plus docs/development/10-current-status.md and docs/development/03-feature-changelog.md if they exist, to see plan vs reality.docs/product/06-roadmap.md: phases, per-phase scope, priorities, and launch readiness. Mark deferred items explicitly instead of deleting them./zno-feature, /zno-plan, ...).<skills-root>/zno-init/references/docs-map.md — full doc set, doc update rules, scaffold triggers.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.