run-checklist

name	run-checklist
description	Automatically verify checklist items generated by /checklist command. Runs tests, linters, security scanners, and spec consistency checks to validate implementation against quality criteria.
argument-hint	<feature-name> [ticket-number]
arguments	["feature-name","ticket-number"]
license	MIT
user-invocable	true
agent	haiku
allowed-tools	Read, Write, Edit, Glob, Grep, Bash, TaskCreate, TaskUpdate, TaskList, TaskGet

Run Checklist - Automated Quality Verification

Automatically execute verification commands for checklist items and record results.

Prerequisites

Read the following prerequisite references before execution:

• references/prerequisites_plugin_update.md - Check for plugin updates
• references/prerequisites_principles.md - Read AI-SDD principles document
• references/prerequisites_directory_paths.md - Resolve directory paths using SDD_* environment variables

Language Configuration

Templates are located under templates/${SDD_LANG:-en}/ within this skill directory. The SDD_LANG environment variable determines the language (default: en).

Required Prerequisites

Prerequisite	Verification	Command to Generate
Checklist	${CLAUDE_PROJECT_DIR}/${SDD_TASK_PATH}/{ticket}/checklist.md exists	/checklist {feature} {ticket}

Input

• feature-name: $feature-name
• ticket-number: $ticket-number

Full argument string: $ARGUMENTS

Fallback: If a value above is empty, remains a literal $ placeholder, or starts with -- (a flag captured positionally), treat that argument as omitted and interpret the full argument string instead. Ask the user interactively when a required argument is missing.

Argument	Required	Description
feature-name	Yes	Target feature name or path (e.g., user-auth, auth/user-login)
ticket-number	-	Task directory name. Uses feature-name if omitted
--category	-	Run only specific category (e.g., --category testing)
--priority	-	Run only specific priority level (e.g., --priority P1)

Input Format

• /run-checklist {feature-name} {ticket-number}
• /run-checklist {feature-name} (uses feature-name as ticket directory)
• /run-checklist {feature-name} {ticket-number} --category testing
• /run-checklist {feature-name} {ticket-number} --priority P1

Processing Flow

1. Load Checklist

Load the checklist file from ${CLAUDE_PROJECT_DIR}/${SDD_TASK_PATH}/{ticket}/checklist.md.

Parse each checklist item:

• Extract CHK-ID (e.g., CHK-501)
• Extract priority level (P1, P2, P3)
• Extract verification commands from code blocks
• Identify category from ID prefix (CHK-1xx = Requirements, CHK-5xx = Testing, etc.)

2. Detect Project Environment

Detect project type and available tools:

Detection Target	Check Method
Package Manager	Check for package.json, Cargo.toml, etc.
Test Framework	Parse config files (jest, pytest, etc.)
Linter	Check for .eslintrc, ruff.toml, etc.
Type Checker	Check for tsconfig.json, mypy.ini, etc.
Security Scanner	Check for audit commands availability

3. Execute Automated Verifications

Read references/verification_commands.md for the verification command mapping table.

Verification Categories

Category (CHK-xxx)	Auto-Verifiable	Verification Method
Requirements (1xx)	Partial	/check-spec for spec consistency
Specification (2xx)	Partial	Type checking, API signature validation
Design (3xx)	Partial	Dependency analysis, architecture checks
Implementation (4xx)	Yes	Linter, static analysis
Testing (5xx)	Yes	Test execution, coverage measurement
Documentation (6xx)	Partial	Doc coverage tools
Security (7xx)	Yes	Security scanners, audit commands
Performance (8xx)	Partial	Benchmark tools (if configured)
Deployment (9xx)	Partial	Config validation

4. Record Results

Read templates/${SDD_LANG:-en}/result_format.md for the result format template.

Update checklist file with verification results:

• Mark verified items with [x] or [ ]
• Add verification timestamp
• Include command output summary

5. Generate Report

Read templates/${SDD_LANG:-en}/report_format.md for the report format template.

Output verification summary to ${CLAUDE_PROJECT_DIR}/${SDD_TASK_PATH}/{ticket}/verification_report.md.

Output Format

Updated Checklist

Original checklist items are updated with verification status. See templates/${SDD_LANG:-en}/result_format.md for the exact checklist item update format and the Automated Verification Result block format.

Verification Report

Save to: ${CLAUDE_PROJECT_DIR}/${SDD_TASK_PATH}/{ticket}/verification_report.md

TaskList Integration

Use TaskList to track verification progress:

1. Create tasks for each verification category being run
2. Update task status as each category completes
3. Mark completed when all verifications finish

Read templates/${SDD_LANG:-en}/tasklist_patterns.md for TaskList usage patterns.

Error Handling

Test Failure

When tests fail, record the failure details and continue with other verifications. See the "Failure Details Format" section in templates/${SDD_LANG:-en}/result_format.md.

Tool Not Available

When a verification tool is not configured, record Status: SKIPPED with the reason and a suggestion (e.g., "ESLint not configured in this project" / "Add .eslintrc to enable linting verification"), using the Automated Verification Result block format from templates/${SDD_LANG:-en}/result_format.md.

Best Practices

Practice	Benefit
Run after implement	Verify implementation meets quality criteria
Run before PR	Ensure all P1 items pass
Use --priority P1	Quick pre-commit verification
Review manual items	Some items require human judgment

Integration with Other Commands

1. /generate-spec {feature}
2. /task-breakdown {feature}
3. /checklist {feature} {ticket} - Generate checklist
4. /implement {feature} {ticket} - Implement feature
5. /run-checklist {feature} {ticket} - Verify implementation
6. Review verification report before PR

Notes

• Not all checklist items can be automatically verified
• Manual verification items are marked for human review
• Results are appended to existing checklist, preserving manual checks
• Run with --category to focus on specific verification types
• Security scanners may require additional setup (npm audit, safety, etc.)