Feature Spec

Feature Spec【免费下载链接】awesome-codex-skillsA curated list of practical Codex skills for automating workflows across the Codex CLI and API.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-codex-skillsOverview[Feature description]RequirementsFunctionalREQ-1: [Requirement]REQ-2: [Requirement]Non-FunctionalPERF-1: [Performance requirement]SEC-1: [Security requirement]Acceptance CriteriaAC-1: [Criterion]AC-2: [Criterion]**提取目标**功能需求列表、非功能需求列表、验收标准列表。仓库中的 User Profile API 规格即是此结构的典型功能需求以 FR-x 编号Get profile、Update profile、Upload avatar 等非功能需求以 NFR-x 编号p95 响应 200ms、1000 并发、GDPR 合规等。 ### 4.2 用户故事驱动型规格User Story Based Spec markdown # Feature Spec ## User Stories ### As a [user type] I want [goal] So that [benefit] **Acceptance Criteria**: - [Criterion] - [Criterion]提取目标用户角色personas、所需能力/目标、每条故事对应的验收标准。4.3 技术设计文档Technical Design Doc# Technical Design ## Problem Statement [Problem description] ## Proposed Solution [Solution approach] ## Architecture [Architecture details] ## Implementation Plan [Implementation approach]提取目标要解决的问题、解决方案思路、架构决策、实现指引。这类结构通常隐含技术选型与权衡解析时要一并记录见下文「技术细节提取」。4.4 产品需求文档PRD# PRD: [Feature] ## Goals [Business goals] ## User Needs [User problems being solved] ## Features [Feature list] ## Success Metrics [How to measure success]提取目标业务目标、用户需求、功能列表、成功指标。PRD 的成功指标可直接映射为实现计划中的「业务成功标准」Business Success这一点在 standard-implementation-plan.md 的模板中有对应落点。五、提取策略Extraction Strategies5.1 需求识别Requirement Identification从规格文本中定位需求信号词与结构标记强约束措辞Must、Should、Will 等情态动词开头的陈述编号需求REQ-1、FR-x、NFR-x 等编号条目用户故事As a… I want… 句式验收标准章节Acceptance Criteria 区块功能列表Features 列表。5.2 需求分类Categorization将识别出的需求按三类归组功能需求Functional——系统做什么用户能力User capabilities系统行为System behaviors数据操作Data operations非功能需求Non-Functional——系统表现如何性能目标Performance targets安全需求Security requirements扩展性需求Scalability needs可用性需求Availability requirements合规需求Compliance requirements约束Constraints——限制条件技术约束Technical constraints业务约束Business constraints时间线约束Timeline constraints分类结果应原样沉淀到实现计划模板的Requirements Summary区块——standard-implementation-plan.md 中分别列出了 Functional Requirements、Non-Functional RequirementsPerformance/Security/Scalability 子项与 Acceptance Criteria与这里的分类维度一一对应。5.3 优先级提取Priority Extraction识别规格中的优先级指示词并映射到实现阶段指示词语义优先级Critical、Must have、P0阻断级/核心P0/CriticalImportant、Should have、P1重要功能P1/HighNice to have、Could have、P2锦上添花P2/MediumFuture、Wont have、P3未来增强P3/Low映射原则按优先级高低分配到实现阶段——P0 进入核心阶段P2/P3 放入后续阶段或明确排除。任务侧同样存在对应体系reference/task-creation.md 将 P0 定义为「阻断其他一切、核心功能、安全需求、数据完整性」P1 为「面向用户的重要功能与性能需求」P2/P3 依次递减两处优先级口径保持了一致。六、处理歧义Handling Ambiguity原文档强调规格解析不是「读完了事」而是要把模糊地带显式文档化为后续计划与任务留下决策记录。6.1 需求不明确Unclear Requirements## Clarifications Needed ### [Requirement ID/Description] **Current text**: [Ambiguous requirement] **Question**: [What needs clarification] **Impact**: [Why this matters for implementation] **Assumed for now**: [Working assumption if any]处理方式创建澄清任务clarification task或在规格页上添加评论。对应到技能整体流程SKILL.md 第 1 步明确要求「在继续之前把缺口/假设记录到 clarifications 区块」。6.2 信息缺失Missing Information## Missing Information - **[Topic]**: Spec doesnt specify [whats missing] - **Impact**: Blocks [affected tasks] - **Action**: Need to [how to resolve]缺失信息要同时写出影响范围阻断哪些任务与解决动作而不是只列缺失项。6.3 需求冲突Conflicting Requirements## Conflicting Requirements **Conflict**: REQ-1 says [X] but REQ-5 says [Y] **Impact**: [Implementation impact] **Resolution needed**: [Decision needed]冲突记录必须明确写出双方原文立场、实现影响与需要谁拍板的决策点。仓库评测 evaluations/README.md 在「创建新评测」一节专门提示要覆盖「模糊规格、冲突需求、缺失细节」等边界场景可见歧义处理是被视为技能核心能力而非可选项的。七、验收标准解析Acceptance Criteria Parsing验收标准是任务验收的直接依据原文档将其分为三类7.1 显式标准Explicit Criteria规格中直接给出的验收标准转换为任务可勾选的 checklist## Acceptance Criteria - User can log in with email and password - System sends confirmation email - Session expires after 24 hours转换为User can log in with email and passwordSystem sends confirmation emailSession expires after 24 hours7.2 隐式标准Implicit Criteria从需求推导出的隐含验收标准Requirement: Users can upload files up to 100MB Implied acceptance criteria: - [ ] Files up to 100MB upload successfully - [ ] Files over 100MB are rejected with error message - [ ] Progress indicator shows during upload - [ ] Upload can be cancelled【免费下载链接】awesome-codex-skillsA curated list of practical Codex skills for automating workflows across the Codex CLI and API.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-codex-skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考