搜索与研究
multica-requirement-analysis
Turn an Issue into a clear, actionable engineering task. Used for requirement clarification, scope confirmation, and acceptance-criteria definition.
it235 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add it235/multica-best-practices --skill multica-requirement-analysis技能说明
name: multica-requirement-analysis description: Turn an Issue into a clear, actionable engineering task. Used for requirement clarification, scope confirmation, and acceptance-criteria definition.
Requirement Analysis
Purpose
Turn an Issue into a clear, actionable engineering task.
Process
- Identify the business goal.
- Identify the expected behavior.
- Identify the explicit scope.
- Identify the non-goals.
- Identify the constraints.
- Identify the acceptance criteria.
- Identify ambiguities.
- Identify dependencies.
Output
- Goal: what problem to solve
- Scope: what will change
- Non-goals: what explicitly won't change
- Acceptance criteria: testable check items
- Constraints: compatibility / performance / security / time
- Dependencies: prerequisites
- Open questions: items needing clarification
Rule
Don't silently digest ambiguous requirements.
If an ambiguity would materially affect the implementation:
→ BLOCKED → Ask for clarification.
Why this works
Ambiguity at the requirement stage gets amplified at every later stage. Blocking ambiguity with BLOCKED is far cheaper than letting 5 Agents each guess differently.