analyze-requirements
技能(Skill):分析需求
目的 (Purpose)
诊断需求层面的问题,将模糊的意图转化为有效的、可测试的需求。引导开发人员从“我想构建 X”到明确的问题陈述、优先需求、明确的约束和有限的范围——所有这些都在任何设计或实施开始之前。
核心目标(Core Objective)
首要目标:生成一份已验证的需求文档,其中每个需求都是可测试的、范围明确的并且以实际问题为基础。
成功标准(必须满足所有要求):
- ✅ 明确的问题:存在明确的问题陈述,但未引用任何解决方案或技术
- ✅ 需求可通过 ID 进行测试:每个需求都有验收标准和唯一的“R-NN”ID(例如 R-01、R-02); ID 连续,无间隙或重复
- ✅ 列出的约束:实际约束(预算、时间、技能、依赖性)与假设分离
- ✅ 范围有限:V1 边界是明确的,列出了延迟的项目并触发重新考虑记录
- ✅ 用户确认:用户明确批准已验证需求(表示“已批准”、“看起来不错”、“继续”或同等内容)
More from nesnilnehc/ai-cortex
review-codebase
Review given file/dir/repo for current-state code organization: module boundaries, design patterns, cross-module dependencies, tech debt, and interface stability. Scope-only atomic skill; output is a findings list.
106review-vue
Review Vue 3 code for Composition API, reactivity, components, state (Pinia), routing, and performance. Framework-only atomic skill; output is a findings list.
94review-diff
Review only git diff for impact, regression, correctness, compatibility, and side effects. Scope-only atomic skill; output is a findings list for aggregation.
91review-java
Review Java code for language and runtime conventions: concurrency, exceptions, try-with-resources, API versioning, collections and Streams, NIO, and testability. Language-only atomic skill; output is a findings list.
84review-architecture
Review code for architecture: module and layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling. Cognitive-only atomic skill; output is a findings list.
83review-security
Review code for security: injection, sensitive data, auth, dependencies, config, and crypto. Atomic skill; output is a findings list.
74