Skip to content
Back to skills

Checklist Design

ASecurity

checklist design principle. checklist-designer agent execution inspectiontable and quality designto do when reference. 'checklist design', 'quality ', 'inspectiontable writing' request when usage. However, checklist development specialist whensystem building scope outside.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
businessgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add chodolmu/taskforge-pro --skill checklist-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Checklist Design?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Checklist Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/chodolmu-checklist-design/badge)](https://www.skillsdirectory.com/skills/chodolmu-checklist-design)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: checklist-design
description: "checklist design principle. checklist-designer agent execution inspectiontable and quality designto do when reference. 'checklist design', 'quality ', 'inspectiontable writing' request when usage. However, checklist development specialist whensystem building scope outside."
---

# Checklist Design — checklist design principle

checklist-designer agent checklist quality design principle and pattern.

## checklist type classification

### Atul Gawande classification (The Checklist Manifesto)

| type | description | usage timing |
|------|------|----------|
| DO-CONFIRM | task after confirm | specialist basis00M dependency degree |
| READ-DO | orderversus execution | reportspecialist/basis task/risk task |
| COMMUNICATION | team between information deliver | personnumberpersontotal, versus |

### SOP annualtotal type

| checklist type | SOP mapping | examplewhen |
|---------------|---------|------|
| companybefore inspection | procedure whenwork before preparation confirm | equipment inspection, re- preparation |
| stageby confirm | each procedure stage complete confirm | , quality company |
| complete verify | procedure after result confirm | final number, personnumber standard |
| basis company | cyclequality operations status inspection | monthbetween planbefore inspection, minutebasis company |

## checklist writing 7principle

### 1. MECE (Mutually Exclusive, Collectively Exhaustive)
- item between during None
- overall 
- categoryby 

### 2. item = confirm
** example**: "from status and annual confirm"
** example**: "from process execution duringpersondegree confirm" + " ping confirm"

### 3. verify possibleKorean standard specify
** example**: " also qualityKoreandegree confirm"
** example**: " also 18~22°C scopepersondegree confirm ( position: during from)"

### 4. 5~9item rule (Killer Items during)
- overall item during core risk item only by
- 9item exceeding when category minute
- " also planbeforeKorean item" 

### 5. order = task flow
- actual task order and dayvalue
- dependency total reflected (A complete after B)

### 6. example processing 
- fail when action procedure specify
- standard included

### 7. cyclequality items
- usage feedback reflected (minutebasis 1)
- company/personwhen after i.e.when 

## checklist template

### READ-DO checklist (stageby execution)

```markdown
# [taskpeople] checklist
- version: v1.0 | final revision: 2025-01-15 | person: 

## companybefore preparation
-  needed tool/re- preparation?
-  task authority confirm?
-  before stage deliverable personnumber?

## execution stage
-  stage 1: [specific action] → standard: [figure/condition]
-  stage 2: [specific action] → standard: [figure/condition]
-  stage 3: [specific action] → standard: [figure/condition]

## complete confirm
-  deliverable standard : [standard]
-  next stage person responsibleto persontotal?

## fail when action
- standard un- item → [person responsible]to reporting
- re-task needed when → [procedure] reference
```

### DO-CONFIRM checklist (companyafter confirm)

```markdown
# [taskpeople] confirm checklist
- daywhen: ______ | confirmspecialist: ______

| # | confirm item | standard | result | notes |
|---|----------|------|------|------|
| 1 | [item] | [standard] | □pass □fail | |
| 2 | [item] | [standard] | □pass □fail | |

- total ___case during pass ___case, fail ___case
- fail action: ___________________
```

## quality design

### standard setting

| element | description |
|------|------|
| standard | company basis for minimum condition |
| required item | mustwhen item (1case also failure when fail) |
| optional item | fail also conditiondepartment and possible |
| and standard | required 100% + optional N% or more |
| conditiondepartment and | when action plan when Koreanwhenquality |

### review process

```
1. deliverable ( specialistto)
2. checklist based review
3. : PASS / CONDITIONAL / FAIL
4. CONDITIONAL: when deadline setting → re-company
5. FAIL: before stage exchange → re-task
```

## checklist quality checklist

| item | standard |
|------|------|
| item number | category 5~9items |
| verify standard | all item quality standard |
| example | fail when action specify |
| responsibilityspecialist | confirmspecialist/approver specify |
| version information | version, date, approver |
| consistency | SOP procedure document and day |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.