Skip to content
Back to skills

4 Prep

ASecurity

Phase 4 — Pre-execution readiness gate. Outputs: home_plans/<project>/prep-checklist.md

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 20, 2026
devops

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add tstapler/dotfiles --skill 4-prep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 4 Prep?

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

Security grade badge for 4 Prep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-4-prep/badge)](https://www.skillsdirectory.com/skills/tstapler-4-prep)

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
---
description: "Phase 4 — Pre-execution readiness gate. Outputs: home_plans/<project>/prep-checklist.md"
user-invocable: true
---

# home:4-prep

Build a pre-execution readiness checklist from the project plan and run the readiness gate. **Do not start physical work until this gate passes.**

## HARD GATE

If any BLOCKER items are unchecked, work must not begin. Blockers are safety hazards, missing permits, or unavailable materials that will halt progress mid-job.

## Instructions

1. **Follow [SETUP.md](SETUP.md)** — identify PROJECT_NAME, and mark this stage's task `in_progress` if a task tool is available (Check 3).

2. **Entry gate — read required inputs:**
   - `home_plans/<PROJECT_NAME>/plan.md` — halt if missing, run `/home:3-plan` first
   - `home_plans/<PROJECT_NAME>/scope.md`
   - `home_plans/<PROJECT_NAME>/adversarial-review.md` (if present)

3. **Write `home_plans/<PROJECT_NAME>/prep-checklist.md`** based on the plan:

```markdown
# Pre-Execution Checklist: <PROJECT_NAME>

**Date**: <YYYY-MM-DD>
**Planned Start**: <date or "TBD">

---

## 🚫 Permits & Regulatory
- [ ] <permit type> — obtained? (or: not required for this project)

---

## 🛒 Materials
<!-- One line per item from the materials list in plan.md -->
- [ ] <Item name> — <qty> — from <source> — ~$<cost>
- [ ] ...

**Materials total**: ~$<X>

---

## 🔧 Tools
- [ ] <tool> — owned / rented (rent from: <where>, ~$<X>/day)
- [ ] ...

---

## 🏠 Space Preparation
- [ ] Area cleared and furniture moved
- [ ] Drop cloths / floor protection in place
- [ ] <any other prep specific to this project>

---

## 🐾 Occupant & Pet Safety
- [ ] Plan for Mochi during hazardous phases: <specify — kennel, back yard, another room>
- [ ] <Any toxic fumes, sharp debris, or access restriction steps>

---

## ⚡ Utility Shutoffs Required Before Starting
- [ ] <e.g., "Shut off water at main valve" — or "None required">

---

## 🦺 Safety Gear
- [ ] <PPE items: gloves, eye protection, respirator, knee pads, etc.>

---

## 📋 Outstanding Decisions
<!-- From plan.md Decisions & Open Questions section -->
- [ ] <decision to make before starting>

---

## Readiness Gate

| # | Check | Status |
|---|-------|--------|
| 1 | All materials purchased or confirmed in stock | |
| 2 | All tools available (owned or reserved for rental) | |
| 3 | Required permits obtained (or confirmed not needed) | |
| 4 | Space prepared and area cleared | |
| 5 | Safety precautions understood and gear on hand | |
| 6 | Pet/occupant plan in place for hazardous phases | |
| 7 | All open decisions resolved | |
```

4. **Run the readiness gate inline.** For each criterion:

   | # | Criterion | Pass? |
   |---|-----------|-------|
   | 1 | All materials listed in plan.md are purchased or confirmed available | |
   | 2 | All tools are on hand or a rental reservation exists | |
   | 3 | Permits either obtained or explicitly confirmed not required | |
   | 4 | No BLOCKER items remain in adversarial-review.md (or file absent) | |
   | 5 | All open decisions in plan.md are resolved | |

   Verdict (this is the stage's exit gate — do not advance past NOT READY):
   - **READY** — all criteria met → output summary and proceed.
   - **ALMOST** — minor gaps (tools not yet rented, some materials not purchased) → note what's outstanding, confirm user wants to proceed.
   - **NOT READY** — blockers or permits unresolved → halt with clear list of what must be done first. Do not proceed to `/home:5-execute`.

5. **Mark this stage's task `completed`** if a task tool is available and the verdict is READY or ALMOST (leave it `in_progress` if NOT READY — the gate hasn't passed). **Output the coordinator summary:**
   ```
   ✅ Phase 4 complete — prep-checklist.md written to home_plans/<PROJECT_NAME>/

   Materials ready: <N>/<N>
   Tools ready: <N>/<N>
   Permits: <obtained / not required / MISSING>
   Readiness gate: <READY|ALMOST|NOT READY>

   Next step: /home:5-execute
   ```

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…