소스 정보
- 저장소
- nWave-ai/nWave
- 최근 소스 활동
- 2026년 3월 25일 09:12
- 감지된 SKILL.md 언어
- 영어
- 스타
- 594
- 포크
- 62
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/nWave-ai/nWave --skill nw-par-review-criteria명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
| name | nw-par-review-criteria |
| description | Quality dimensions and review checklist for devop reviews |
| user-invocable | false |
| disable-model-invocation | true |
Pattern: Phase handoffs missing required artifacts or approvals.
Required per Phase:
Severity: critical. Verify all artifacts present and peer-reviewed before phase transition.
Pattern: Feature marked "ready" but missing production prerequisites.
Required: All tests passing (100%) | Production configuration complete | Monitoring/alerting configured | Runbook/operational docs created | Rollback plan documented.
Severity: critical. Complete missing prerequisite before marking deployment-ready.
Pattern: Cannot trace production code back to requirements.
Required: User stories map to acceptance tests | Acceptance tests map to production code | Code changes traceable to commits | All AC verified in production.
Severity: high. Establish traceability chain: user-story -> acceptance-tests -> code-commits.
Purpose: Validate roadmap addresses largest bottleneck first, not secondary concern.
Q1: Is this the largest bottleneck? Does timing data show primary problem? Larger problem being ignored? Assessment: YES / NO / UNCLEAR.
Q2: Were simpler alternatives considered? Roadmap includes rejected alternatives? Rejection reasons evidence-based? Simpler solution achieves 80% benefit? Assessment: ADEQUATE / INADEQUATE / MISSING.
Q3: Is constraint prioritization correct? Constraints quantified by impact? Architecture addresses constraint-free opportunities first? Minority constraint dominating? (flag if >50% of solution for <30% of problem). Assessment: CORRECT / INVERTED / NOT_ANALYZED.
Q4: Is architecture data-justified? Key architectural decision supported by quantitative data? Different data leads to different architecture? Assessment: JUSTIFIED / UNJUSTIFIED / NO_DATA.
Purpose: Verify feature wired into system entry point -- prevents Testing Theatre. A feature with 100% test coverage but 0% wiring tests is not complete.
Validation Criteria:
Gate failure response: Block finalization | report specific integration gap with evidence | require integration step before completion.