Checklist DesignSAFE

An agent skill published by revfactory.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
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 |

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.