Generate a custom requirements quality checklist for Go/infrastructure changes. Validates that requirements are complete and clear.
Create domain-specific checklists that test whether requirements are well-written, NOT whether the implementation works.
/checklist [domain]
Examples:
/checklist performance - Create a performance requirements checklist/checklist security - Create a security requirements checklist/checklist concurrency - Create a concurrency safety checklist/checklist deployment - Create a deployment requirements checklistLoad feature context:
git branch --show-currentspecs/in-progress/[branch-name]/specs/backlog/[branch-name]/specs/completed/[branch-name]/specs/[branch-name]/ (legacy fallback){resolved-spec-dir}/spec.md and plan.mdCLAUDE.mdClarify intent (up to 3 questions):
{{args}}Generate checklist with items grouped by quality dimension:
| Dimension | What it checks |
|---|---|
| Completeness | Are all necessary requirements present? |
| Clarity | Are requirements specific and unambiguous? |
| Consistency | Do requirements align without conflicts? |
| Measurability | Can requirements be objectively verified? |
| Coverage | Are all scenarios/edge cases addressed? |
| Config Coherence | Do env vars, Helm values, and Go struct tags align? |
| Dependencies | Are infrastructure assumptions documented? |
Domain-specific checks:
| Domain | Additional checks |
|---|---|
| performance | Connection limits, rate limits, resource requests/limits, backpressure thresholds |
| security | Input validation, JWT, tenant isolation, secrets management, rate limiting |
| concurrency | Goroutine lifecycle, mutex scope, atomic usage, channel safety, panic recovery |
| deployment | Helm values, Terraform variables, image tags, rollback plan, health checks |
| kafka | Consumer groups, topic naming, offset management, partition strategy, backpressure |
| monitoring | Prometheus metrics naming, label cardinality, dashboard queries, alert thresholds |
Item format:
- [ ] CHK001 Are [requirement type] defined for [scenario]? [Quality Dimension]
Write checklist to {resolved-spec-dir}/checklist-[DOMAIN].md
Report: File path, item count, focus areas, suggested next steps
/checklist run creates a NEW file (never overwrites existing ones)