菜单
Validates code, specifications, and tasks against project requirements using Straion's semantic matching. Use when checking compliance, validating PRs, reviewing specs against requirements, or when user asks "does this meet requirements", "check compliance", "validate this".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides users through requirements-first feature implementation from idea to production code. Validates specs, tasks, and implementation against project requirements at every step. Use when building features, implementing specs, creating implementation plans, breaking down specs into tasks, or when user says "help me build", "implement this", "add feature", "plan this", "break down this spec", "create tasks", or wants requirements compliance.
Guides users through rules-first feature implementation from idea to production code. Validates specs, tasks, and implementation against project rules at every step. Use when building features, implementing specs, creating implementation plans, breaking down specs into tasks, or when user says "help me build", "implement this", "add feature", "plan this", "break down this spec", "create tasks", or wants rules compliance.
Validates code, specifications, and tasks against project rules using Straion's semantic matching. Use when checking compliance, validating PRs, reviewing specs against rules, or when user asks "does this meet rules", "check compliance", "validate this".
| name | validating-requirements |
| description | Validates code, specifications, and tasks against project requirements using Straion's semantic matching. Use when checking compliance, validating PRs, reviewing specs against requirements, or when user asks "does this meet requirements", "check compliance", "validate this". |
straion find-requirements — see ../shared/STRAION_CLI.md| Level | What | Check Against |
|---|---|---|
| Spec | PRDs, ADRs, RFCs | Architecture, security, design principles |
| Task | Implementation tasks | Technical requirements, API contracts, testing |
| Code | Actual changes | Coding standards, security, performance |
For each requirement returned by the CLI:
## Requirements Validation Report
### Summary
[X requirements checked, Y compliant, Z issues]
### Compliant ✅
- **REQ-123**: [Requirement summary] — ✅ [What was done correctly]
### Partial Compliance ⚠️
- **REQ-456**: [Requirement summary] — ⚠️ [What's missing]
- **Recommendation**: [Specific fix]
### Violations ❌
- **REQ-789**: [Requirement summary] — ❌ [The violation]
- **Risk**: [Impact]
- **Fix**: [Concrete solution]
When violations are found: