45ck formal-inspection-facilitator
Purpose
Run a structured formal inspection with defined roles, entry criteria, defect logging, and rework follow-up.
Trigger this skill when
- You need a focused code-review or inspection analysis or artifact rather than generic commentary.
- Review discipline, issue handling, or closure quality matters to the outcome.
- You need a reusable output another reviewer, developer, or agent can extend safely.
Expected inputs
- inspection context and artifact under review
- participants or roles
- review objectives and criteria
- known constraints or deadlines
Deliverables
- inspection plan or findings
- defect log or review summary
- assumptions and unresolved questions
- recommended next skill
Operating procedure
- Clarify the artifact, review objective, and what counts as a meaningful issue.
- Separate explicit evidence from assumptions, missing context, or inference.
- Apply the relevant review structure, checklist, or inspection framing consistently.
- Produce compact findings that support triage, rework, and decision-making.
- Recommend the next most useful review, remediation, readiness, or process step.
Quality gates
- Do not treat preference as defect unless the criterion is explicit.
- Make severity, uncertainty, and evidence quality explicit.
- Prefer actionable findings tied to consequence over vague style commentary.
- Keep the artifact compact, structured, and reusable.
Handoff targets
- review-issue-categorizer
- review-severity-scorer
- rework-plan-writer
Output style
- Be explicit about evidence quality and uncertainty.
- Prefer structured findings over narrative filler.
- Tie recommendations to risk, delivery consequence, or rework cost.
- Use severity, priority, or confidence labels when useful.
Failure modes to avoid
- Do not collapse all issues into one undifferentiated list.
- Do not hide missing evidence, unclear criteria, or reviewer uncertainty.
- Do not recommend vague actions with no owner or closure path.
- Do not ignore process defects when the artifact issues are symptoms of review failure.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Evidence / confidence
## Assumptions
## Open questions
## Recommended next skill