菜单
Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/athola/claude-night-market --skill spec-writing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | spec-writing |
| description | Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning. |
| alwaysApply | false |
| category | specification |
| tags | ["speckit","specification","requirements","user-stories","acceptance-criteria"] |
| dependencies | ["superpowers:brainstorming"] |
| tools | [] |
| usage_patterns | ["feature-specification","requirements-documentation","user-story-creation"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 1200 |
| progressive_loading | true |
| modules | ["modules/success-criteria-patterns.md","modules/specification-structure.md","modules/checklist-dimensions.md"] |
Create clear, complete, and testable specifications from natural language feature descriptions. Specifications focus on user value and business needs, avoiding implementation details.
Focus on user value and business needs rather than implementation details. Avoid specifying technology choices in requirement definitions unless strictly necessary. Ensure every requirement is testable and verifiable with measurable criteria. Limit clarification markers; make informed assumptions based on industry standards and document them explicitly.
See: modules/specification-structure.md for detailed templates and guidelines
See: modules/success-criteria-patterns.md for detailed examples and conversion process
speckit-orchestrator: Workflow coordinationtask-planning: Converting specs to tasksIf specifications are too vague, use the success-criteria-patterns
module to enforce measurable outcomes. If implementation details leak
into specs, review against the "Core Principles" and refactor to focus
on user behavior.
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.