菜单
Convert requirements into a structured technical specification. Use when starting a new feature or receiving vague requirements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design system architecture and decompose work into Acts with tasks, dependencies, and cycle budgets. Use after a spec is approved, before coding begins.
Review, test, slop-check, then commit and optionally open a PR. The ship pipeline: one command from "code complete" to "committed and reviewed."
Show all UV Suite skills, agents, hooks, guardrails, and personas. Use when you want to know what's available or how to use a specific feature.
Systematic root-cause debugging. Traces data flow, tests hypotheses, narrows scope. Stops after 3 failed attempts and escalates. Use when something is broken and you don't know why.
Toggle lite mode — instructs the assistant to be terse (no preamble, no summaries, no decorative formatting). Use when tokens are limited or you just want shorter answers. Persists across turns until disabled.
Build an interactive prototype as a static React site. For concept exploration, stakeholder demos, presentations, and documentation websites.
| name | uvs-spec |
| description | Convert requirements into a structured technical specification. Use when starting a new feature or receiving vague requirements. |
| argument-hint | [requirements-description] |
| user-invocable | true |
| context | fork |
| agent | spec-writer |
| model | claude-opus-4-6 |
| effort | high |
| allowed-tools | ["Read(*)","Grep(*)","Glob(*)","Write(uv-out/**)","AskUserQuestion"] |
$ARGUMENTS
Write the spec under this directory (it is scoped to the current session, so artifacts are attributable to the session that produced them):
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-session.sh
The codebase map, prior specs, and decisions for this project are auto-loaded below (from
uv-out/). Read them first — they are the indexed view of the existing codebase. Then use
AskUserQuestion to ask the user only for what those don't cover: specific files, modules,
API contracts, or data models the spec must account for. Read every file they name before
drafting. Greenfield (no map, no relevant code) → proceed without. Don't guess at relevant
files — ground in the map or ask.
!cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found"
!ls -la docs/architecture* 2>/dev/null || echo "No architecture docs found"
Prior UV Suite artifacts for THIS project. Ground the spec in them — reference real modules and patterns from the map, reuse existing conventions, and build on (don't re-spec) what's already captured.
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh map-codebase.md 120 || echo "No codebase map — run /uvs-understand first for a grounded spec"
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh map-stack.md 80 || echo "No stack map"
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'specs/*.md' 80 || echo "No prior specs"
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'architecture/decisions.md' 60 || echo "No architecture decisions found"
!date +%Y-%m-%d
