메뉴
Validates implemented code against technical specifications, runs comprehensive tests, and ensures alignment before merge. Third prong of the development workflow after planning and orchestration.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/l3wi/agents-workflow --skill validate-plan명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | validate-plan |
| description | Validates implemented code against technical specifications, runs comprehensive tests, and ensures alignment before merge. Third prong of the development workflow after planning and orchestration. |
Comprehensive validation of implemented features against their technical specifications. Ensures code quality, test coverage, and spec compliance before final merge.
/skill:swarmfeat/{feature-name} branchdocs/specs/{feature-name}-spec.md exists/skill:validate <feature-name> # Full validation suite
/skill:validate <feature-name> --tests-only # Run tests only, skip spec alignment
/skill:validate <feature-name> --spec-only # Check spec alignment only, skip tests
/skill:validate <feature-name> --coverage-only # Check test coverage only
/skill:validate <feature-name> --fix # Auto-fix issues where possible
feat/{feature-name}Load Context
docs/specs/{feature-name}-spec.mdCode Analysis
Alignment Verification
Generate Alignment Report
Unit Tests
npm test or equivalentIntegration Tests (for non-UI components)
End-to-End Tests
Coverage Analysis
# Generate detailed coverage report
npm run test:coverage
# Check coverage thresholds
# Report on areas lacking coverage
Validate against these criteria:
Generate comprehensive report at docs/validation/{feature-name}-validation.md:
# Validation Report: {feature-name}
**Date**: {timestamp}
**Branch**: feat/{feature-name}
**Spec**: docs/specs/{feature-name}-spec.md
**Status**: ✅ PASS | ⚠️ PARTIAL | ❌ FAIL
## Summary
- Tests: {passed}/{total} passing
- Coverage: {percentage}% (target: 80%)
- Spec Alignment: {percentage}% complete
## Test Results
### Unit Tests
- Coverage: {percentage}%
- Passing: {count}
- Failing: {count}
### Integration Tests
- Endpoints tested: {count}
- Database ops: ✅/❌
- External services: ✅/❌
### E2E Tests
- Critical paths: {passed}/{total}
## Spec Alignment
### Implemented ✅
- [List of correctly implemented features]
### Deviations ⚠️
- [List of partial/different implementations]
### Missing ❌
- [List of missing implementations]
## Recommendations
- [Specific fixes needed]
- [Optional improvements]
## Approval Status
- [ ] Ready for merge
- [ ] Requires fixes (see recommendations)
Attempt automatic fixes for common issues:
| Status | Criteria | Action |
|---|---|---|
| ✅ PASS | All tests pass, 80%+ coverage, full spec alignment | Approve for merge |
| ⚠️ PARTIAL | Tests pass, good coverage, minor spec gaps | Review recommendations, may proceed |
| ❌ FAIL | Test failures, low coverage, or major spec gaps | Block merge, remediation required |
# Complete development workflow:
/skill:plan feature-name # PRD → Spec → Tasks
/skill:swarm feature-name # Plan and implement
/skill:validate feature-name # Validate and approve
# If validation fails:
/skill:validate feature-name --fix # Auto-fix common issues
# Manual fixes in feature branch
/skill:validate feature-name # Re-validate
# When validation passes:
# Manual merge of feat/{feature-name} to dev
User: /skill:validate user-avatar
Pi: Starting validation for user-avatar...
## Environment Setup
✅ Switched to feat/user-avatar
✅ Dependencies up to date
✅ Test infrastructure ready
## Spec Alignment Analysis
📖 Loading spec: docs/specs/user-avatar-spec.md
🔍 Analyzing implemented code...
### API Endpoints
✅ POST /api/avatar/upload - matches spec
✅ GET /api/avatar/{userId} - matches spec
⚠️ DELETE /api/avatar/{userId} - missing error handling for 404
### Data Models
✅ Avatar schema matches spec
✅ Database migrations present
### Security
✅ File type validation implemented
✅ Size limits enforced
❌ Missing rate limiting (spec requirement)
## Test Execution
### Unit Tests
✅ 127/127 tests passing
✅ Coverage: 85% (target: 80%)
### Integration Tests
✅ API endpoints: 12/12 passing
✅ Database operations: 5/5 passing
✅ File upload flow: 3/3 passing
### E2E Tests
✅ Avatar upload flow: 2/2 passing
⚠️ Avatar deletion flow: 1/1 passing (but missing rate limit test)
## Validation Summary
- **Status**: ⚠️ PARTIAL
- **Tests**: 143/143 passing (100%)
- **Coverage**: 85%
- **Spec Alignment**: 90%
## Issues Found
❌ Missing rate limiting implementation
⚠️ Incomplete error handling in delete endpoint
## Recommendations
1. Add rate limiting middleware to avatar endpoints
2. Improve error handling for 404 cases
3. Add integration test for rate limiting
Validation report saved: docs/validation/user-avatar-validation.md
Would you like me to attempt automatic fixes with /skill:validate user-avatar --fix?
When validation fails, use standard development workflow:
npm test/skill:validate feature-nameOptional validation config at .validate.json:
{
"coverage": {
"unit": 80,
"integration": 70,
"e2e": 50
},
"testCommand": "npm test",
"coverageCommand": "npm run test:coverage",
"e2eCommand": "npm run test:e2e",
"autoFix": ["coverage", "docs", "types"],
"strictMode": false
}
/skill:swarm - Implementation planning and orchestration/skill:plan - Planning workflow (PRD → Spec → Tasks)/skill:feature - Single-branch feature implementationdocs/validation/ - Validation reports storage