# Docfill P0.6 Freeze Implementation Plan

> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.

**Goal:** Freeze the current MVP as a small deliverable that can be built, smoke-tested, and handed to a digital employee.

**Architecture:** Keep the current single-command CLI and add only delivery wrappers: a local build script, a runbook, and ignore rules for generated artifacts. No new runtime features.

**Tech Stack:** Go, shell, existing `docfill run` CLI.

---

### Task 1: Build Output

**Files:**
- Modify: `.gitignore`
- Create: `scripts/build.sh`

- [ ] Ignore `dist/`.
- [ ] Build only the current machine target into `dist/docfill-darwin-arm64`.
- [ ] Print the output path.

### Task 2: Digital Employee Runbook

**Files:**
- Create: `docs/digital-employee-runbook.md`
- Modify: `README.md`

- [ ] Document required inputs, command contract, stdout/stderr handling, exit codes, and common errors.
- [ ] Link the runbook from README.

### Task 3: Freeze Verification

- [ ] Run `go test -count=1 ./...`.
- [ ] Run `bash scripts/smoke.sh`.
- [ ] Run `bash scripts/build.sh`.
- [ ] Stage all project files except local ignored files.
- [ ] Commit as `feat: add docfill mvp cli`.