Phase 7 of the SRS workflow. Runs srs_validator.py --dir on the generated SRS files, reports errors and warnings, auto-fixes ERRORs, and outputs a COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT verdict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Goal: validate the generated SRS against IEEE 830-1998. Fix all ERRORs before reporting. WARNings are captured for the improvement report.
AskUserQuestion: "Which project to validate? (slug)"
Check that projects/{slug}/srs/ exists and contains .md files.
If missing: tell user to run /sr:generate first.
Execute:
python .claude/scripts/srs_validator.py --dir projects/{slug}/srs/
Capture stdout. Display the full validation table.
For each ERROR finding:
missing-section: add the section with correct heading formatfr-no-shall: rewrite the Requirement line with explicit "shall" clausefr-numbering-gap: renumber FRs to fill gaps (update all references)FIXED [ERROR] fr-no-shall in FR-07 → added "shall" clauseAfter fixing all ERRORs: re-run validator and confirm no new ERRORs.
List all WARN findings but do NOT fix them here — they go into the improvement report.
Format:
WARN: unresolved-tag — 3 [TBD] tags remain (NFR-03, NFR-07, §1.3)
WARN: fr-incomplete-gwt — FR-12: missing "Then:" field
WARN: nfr-no-numeric — NFR-05 Response Measure has no numeric threshold
Output:
## Validation Result
Verdict: COMPLIANT | PARTIALLY COMPLIANT | NON-COMPLIANT
File: projects/{slug}/srs/ ({N} files)
ERRORs fixed: {count}
WARNings open: {count} → captured in /sr:improve report
Next: /sr:improve → improvement report + warning resolution guide
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.