菜单
Analyze consistency across spec, plan, tasks, and checklist. Use before implementation. Triggers on: analyze consistency, check artifacts, validate feature.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate quality validation checklist from spec, plan, and tasks. Use after creating tasks. Triggers on: create checklist, quality checklist, validation checklist.
Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.
Distill learnings from completed features and propose amendments to constitution.md or prompt.md. Use after feature completion. Triggers on: capture learnings, learn from feature, distill learnings, relentless learn.
Generate technical implementation plan from feature specification. Use after creating spec. Triggers on: create plan, technical plan, implementation design.
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Generate dependency-ordered user stories and tasks from plan. Use after creating plan. Triggers on: create tasks, generate user stories, break down implementation.
| name | analyze |
| description | Analyze consistency across spec, plan, tasks, and checklist. Use before implementation. Triggers on: analyze consistency, check artifacts, validate feature. |
Validate consistency across feature artifacts before implementation.
This skill is Step 5 of 6 in the Relentless workflow:
specify → plan → tasks → convert → analyze → implement
Prerequisites (ALL must exist):
spec.md - Feature specificationplan.md - Technical implementation plantasks.md - User stories and tasksprd.json - Converted PRD with routing metadata (run convert first)checklist.md - Quality validation checklist (recommended)Purpose:
Required:
relentless/constitution.mdrelentless/features/NNN-feature/spec.mdrelentless/features/NNN-feature/plan.mdrelentless/features/NNN-feature/tasks.mdrelentless/features/NNN-feature/prd.jsonrelentless/features/NNN-feature/checklist.mdOptional:
relentless/features/NNN-feature/progress.txtVerify that:
Flag as CRITICAL if TDD requirements are missing.
Verify that prd.json contains for EVERY story:
routing.complexity - simple/medium/complex/expertrouting.harness - claude/gemini/codex/opencode/amp/droidrouting.model - specific model namerouting.mode - free/cheap/good/geniusrouting.estimatedCost - cost in USDAlso verify:
Flag as CRITICAL if routing metadata is missing.
Verify that ALL THREE quality gates are present in acceptance criteria:
bun run typecheck passes with 0 errors)bun run lint passes with 0 errors AND 0 warnings)bun test passes)Flag as CRITICAL if any quality gate is missing.
any types plannedCRITICAL: Blocks implementation - MUST fix before proceeding
WARNING: Should fix before implementation
INFO: Nice to have
Use the template at templates/analysis-report.md:
# Consistency Analysis Report
**Feature:** [feature-name]
**Date:** [date]
**Status:** [PASS | FAIL | WARNINGS]
## Summary
| Category | Status | Issues |
|----------|--------|--------|
| Completeness | ✅/❌ | [count] |
| TDD Compliance | ✅/❌ | [count] |
| Routing Validation | ✅/❌ | [count] |
| Quality Gates | ✅/❌ | [count] |
| Constitution | ✅/❌ | [count] |
| Dependencies | ✅/❌ | [count] |
## Critical Issues
### CRIT-001: [Issue Title]
**Location:** [file]
**Details:** [description]
**Fix:** [required action]
## Recommendations
1. [Action item 1]
2. [Action item 2]
**Next Step:** /relentless.implement (if PASS) or fix issues (if FAIL)
relentless/features/NNN-feature/analysis-report.md/relentless.implement or fix issues