jsdlc-review

# Artifact Review (レビュー) Request / arguments: $ARGUMENTS This is the general entry point. If the target is clearly one artifact type, prefer its own skill — `/jsdlc-detail-design review <file>` and the rest carry artifact-specific guidance this skill does not repeat. Use this skill when: the target type is mixed or unclear, several documents are reviewed together, or the user wants a consistency check across the chain. Read `docs-jsdlc/rules/review-checklist.md` in full before starting. ## Procedure ### 1. Identify targets and their types List every document under review with its type and version. For each, identify its parent and read it — a review that never opens the parent cannot check traceability, which is the highest-severity category. ### 2. Select the checklist sections Always §2 (common). Then §3 basic design, §4 detail design, §5 API spec, §6 test case, §7 implementation, as applicable. ### 3. Run checks one at a time For each check ID: read the relevant part, decide OK / NG / 要確認, and record evidence — a quotation or a precise location. A check marked OK without having been looked for is the failure mode that makes reviews worthless. Count the checks run. Name the ones not applicable and why. ### 4. Cross-document consistency (when reviewing more than one) - error codes: defined in basic design, used unchanged downstream - terminology: one concept, one term, across all documents - revision consistency: no child older than its parent (要確認) - level skips: no document tracing past an intermediate level ### 5. Classify honestly `NG` only when provable from the documents. `要確認` when it needs a human decision. Do not inflate severity to look thorough, and do not soften an NG to avoid work. Both distort the count the client reads. ### 6. Write the report Use `docs-jsdlc/templates/review-report.md`. Save to `docs-jsdlc/output/review/<target>-review-<YYYYMMDD>.md`. Verdict: **FAIL** if any NG is open, **CONDITIONAL PASS** if only 要確認 remain, **PASS** otherwise. ### 7. Report to the user Verdict, counts by severity, the three most serious findings in one line each, and how many checks ran. Never end with "no problems found" alone. ## Applying findings This skill does not modify documents. To apply findings, run the artifact's own skill in `modify` mode with the review report as input.