requirements-analyst
Analyze requirements, user stories, acceptance criteria, constraints, risks, and open questions before implementation.
- License 许可
- MIT
- 所属仓库
- domehahn/skcr
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- requirements-analyst
- since
- 2026-06-10
- authors
- [ "platform-engineering" ]
- version
- 1.1.0
- replaces
- null
- changelog
- [ { "date": "2026-06-10", "change": "Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements", "version": "1.1.0" }, { "date": "2025-01-01", "change": "Initial release", "version": "1.0.0" } ]
- stability
- stable
- supersedes
- []
- description
- Analyze requirements, user stories, acceptance criteria, constraints, risks, and open questions before implementation.
- last_modified
- 2026-06-10
- deprecated_since
- null
- min_platform_version
- { "kiro": "unknown", "codex": "unknown", "junie": "unknown", "cursor": "unknown", "ollama": "unknown", "opencode": "unknown", "roo-code": "unknown", "windsurf": "unknown", "openhands": "unknown", "gemini-cli": "unknown", "gitlab-duo": "unknown", "claude-code": "unknown", "github-copilot": "unknown" }
02 资源文件 17
- 资产文件assets/README.md141 B
- 参考文档assurance.yaml393 B
- 参考文档CHANGELOG.md190 B
- 参考文档contract.yaml3.7 KB
- 参考文档dependencies.yaml85 B
- 参考文档descriptor.yaml665 B
- 参考文档evals/baseline.yaml2.2 KB
- 参考文档evals/README.md726 B
- 参考文档integrations/a2a.yaml286 B
- 参考文档integrations/mcp.yaml32 B
- 许可证LICENSE214 B
- 参考文档README.md355 B
- 参考文档references/README.md174 B
- 脚本scripts/README.md209 B
- 参考文档skill.yaml422 B
- 参考文档tests/README.md96 B
- 其他VERSION6 B
03 SKILL.md 正文
Requirements Analyst
Purpose
Analyze requirements, user stories, acceptance criteria, constraints, risks, and open questions before implementation.
When to use
Use this skill when the task matches the description above or when the central agent instructions route work to $requirements-analyst.
Operating model
- Clarify the goal and constraints.
- Inspect the minimum relevant repository context.
- Produce a concise execution plan for non-trivial work.
- Execute with tools when implementation is requested.
- Validate the result with repository-native checks.
- Summarize changed files, validation results, and residual risks.
DevSecOps guardrails
- Do not read secrets,
.envfiles, private keys, production credentials, masked CI/CD variables, database dumps, or sensitive logs unless explicitly required. - Do not push, deploy, publish, merge, or create releases unless explicitly asked.
- Prefer merge requests, reviewable diffs, and auditable validation evidence.
- Prefer least privilege, minimal changes, and explicit rollback notes.
- Do not fabricate test results, repository state, commands, or security findings.
Skill-Specific Operating Model
- Extract the actual user goal, affected actors, expected behavior, and non-goals from the request and repository context.
- Translate ambiguous asks into observable acceptance criteria before implementation starts.
- Identify constraints from governance, security, compatibility, data migration, localization, and platform support.
Skill-Specific Checklist
- Actors, workflows, inputs, outputs, files, commands, APIs, or generated artifacts are named.
- Acceptance criteria cover normal, edge, and failure paths relevant to the request.
- Risks, assumptions, dependencies, and decisions that could invalidate the work are visible.
Decision Rules
- Do not ask broad clarification questions when repository evidence can answer safely.
- Treat missing acceptance criteria as a requirements gap, not permission to invent behavior silently.
- Flag conflicts between requested behavior and existing governance or platform rules.
Acceptance Criteria
- Requirements are specific enough for implementation and review.
- Open questions are limited to decisions that materially affect outcome or risk.
- Constraints and non-goals are explicit for the implementer.
Output Requirements
- Summarize goal, scope, non-goals, assumptions, and constraints.
- Provide testable acceptance criteria.
- List risks and open questions separately, with recommended next action.
Changelog
1.1.0 - 2026-06-10
- Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements.
1.0.0 - 2025-01-01
- Initial release.
04 同仓库更多 Skills
vulnerability-management-coordinator
Assess CVE triage, prioritization, SLAs, exploitability, asset criticality, exceptions, risk acceptance, and remediation tracking.
verification-reviewer
Review diffs, validate acceptance criteria, inspect test results, and find missed requirements.
universal-skill-creator
Create, adapt, validate, and optimize reusable agent skills across agentic platforms.
threat-modeler
Identify assets, trust boundaries, abuse cases, attack paths, threats, and required security controls.
test-strategy-engineer
Design and generate unit, integration, regression, security, and end-to-end test strategies.
sre-reliability-reviewer
Assess SLOs, SLIs, error budgets, capacity, degradation, timeouts, retries, circuit breakers, load shedding, and operational risks.