跳到主要内容
知仓学习社ZHICANG

specification-writing

Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.

不碰外部(只输出文字)无严重或高危命中a5c-ai/babysitter

它会碰到什么

扫了多少2 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

  • Formalizing vague feature requests into structured requirements
  • Clarifying scope boundaries for a feature area
  • Establishing acceptance criteria for user stories

Key Principle

Specifications describe desired behavior from the user's perspective. They define what the system should do, not how it should be built. Business value must be explicit in every requirement.

Process

  1. Elicit requirements - Extract functional and non-functional requirements from feature description
  2. Write user stories - Author stories in standard format with personas
  3. Define acceptance criteria - Testable conditions for each story (Given/When/Then)
  4. Identify edge cases - Error scenarios and boundary conditions
  5. Clarify gaps - Surface and resolve ambiguities and contradictions
  6. Document assumptions - Make implicit assumptions explicit
  7. Define scope - Clearly delineate in-scope vs. out-of-scope
  8. Human review - Approve specification before planning

Tool Use

Invoke via babysitter process: methodologies/spec-kit/spec-kit-specification

Full pipeline: methodologies/spec-kit/spec-kit-orchestrator

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。