메뉴
Review a spec document for completeness before approval. Use after interview, before implementation, or when asked to 'review spec', 'check spec', or 'is this spec ready'. Read-only analysis that flags gaps.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/opsMachine/OM-Agency --skill spec-review명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | spec-review |
| description | Review a spec document for completeness before approval. Use after interview, before implementation, or when asked to 'review spec', 'check spec', or 'is this spec ready'. Read-only analysis that flags gaps. |
| allowed-tools | Read, Grep, Glob |
| contract | {"tags":["intake","review","quality-gate"],"state_source":"spec","inputs":{"params":[{"name":"spec_path","required":true}],"gates":[{"field":"status","value":"Draft"}]},"outputs":{"mutates":[],"side_effects":[]},"next":["plan-tests","implement-direct"],"human_gate":true} |
Reviews a specification document for completeness and quality before approval. This is a read-only skill that analyzes without modifying.
Use this skill when:
/spec-review path/to/spec.mdRead the spec document at the path provided by the user.
See shared/spec-io.md for spec file location and section structure.
If no path provided, look for recent specs in Documents/specs/ and ask which one to review.
Gate check: Verify **Status:** is Draft. If already , the spec has been reviewed — nothing to do here.
ApprovedEvaluate each section against these criteria:
Red flags:
Red flags:
Red flags:
Red flags:
Red flags:
Note: This section helps activate falsification (testing if you're wrong BEFORE implementing). It prevents discovering issues through iteration that could be caught upfront.
Acceptable if empty - not all specs need technical notes
Red flags:
See
shared/security-lens.mdfor what good answers look like.
Acceptable if empty - not all interviews surface questions
Rate the spec on this scale:
Ready for Implementation
Needs Minor Revision
Needs Major Revision
Format your response as:
## Spec Review: {spec name}
### Readiness: {Ready | Needs Minor Revision | Needs Major Revision}
### Completeness Checklist
**Problem Statement:** {Complete | Incomplete}
- {specific feedback}
**Acceptance Criteria:** {Complete | Incomplete}
- {specific feedback}
- {count} criteria found
**Non-Goals:** {Complete | Incomplete}
- {specific feedback}
**Assumptions:** {Complete | Incomplete}
- {specific feedback}
**Falsification Analysis:** {Complete | Incomplete}
- {specific feedback}
- Failure modes considered: {yes/no}
**Security Considerations:** {Complete | Incomplete}
- {specific feedback}
### Gaps Found
{List specific gaps if any}
### Suggested Questions
{Questions that might have been missed during interview}
### Recommendation
{Clear next step - approve and proceed, or revise specific sections}
This skill is read-only. Do not:
If revisions are needed, tell the user what to change and let them (or the interview skill) make the updates.
User: /spec-review Documents/specs/42-dark-mode-spec.md
Claude:
## Spec Review: Dark Mode Toggle
### Readiness: Needs Minor Revision
### Completeness Checklist
**Problem Statement:** Complete
- Clear problem: users want dark mode for eye strain
- Impact: affects all users, especially night-time use
- Beneficiary: all application users
**Acceptance Criteria:** Complete
- 4 testable criteria found
- Edge cases covered (persistence, browser support)
**Non-Goals:** Incomplete
- Only says "not doing system-wide theme"
- Should clarify: custom color themes? Per-page themes?
**Assumptions:** Complete
- Assumes CSS variables already in place
- Assumes local storage is acceptable for persistence
### Gaps Found
1. Non-Goals could be more specific about what theme features are deferred
### Suggested Questions
- Should dark mode sync across devices (if user is logged in)?
- What's the default for new users - light or dark?
### Recommendation
Minor revision needed. Add specifics to Non-Goals section and consider the syncing question. Otherwise ready to proceed.
Performs comprehensive, brutally honest full-codebase review as a grumpy but fair senior developer with 20+ years of experience. Use when the user asks for a grumpy dev code review, brutal code review, senior dev review, comprehensive codebase audit, hall-of-shame code smells, or a gut-check on the entire project (not just a PR diff).
Diagnose and fix OneCLI gateway issues — Docker not running, 407 proxy auth, 401 from API (MITM not active), stale aoc_ token, CA cert refresh, secret setup, version pinning. Use when onecliStart fails, update-fathom-db fails, proxy returns 407 or 401, mode=tunnel in logs, or after OneCLI container recreation.
ANY CRM or progress.md write, log call, add contact, pipeline lookup, paste transcript/email. Runs lifecycle routing in Step 0 — delivery work goes to progress.md not Won CRM Next Action. Query before create. For week view use week-scan not this skill. OM-Repo SKILLS-MAP.md.