# Pocdd Verify

> Validate that a POC file is well-formed against the POCDD conventions — status header, the three sections, gaps tagged by owner with ids, findings with provenance, and decision gaps carrying an assumption + link. Read-only pass/fail. Use for "/poc verify <name>".

- Skill: `dailybothq/pocdd-verify` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add dailybothq/pocdd-verify`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dailybothq/pocdd-verify/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dailybothq (https://skillmd.com/u/dailybothq)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dailybothq/pocdd-verify

---


# POCDD — Verify

Objective well-formedness check for a POC file, against
[`../shared/conventions.md`](../shared/conventions.md). Read-only.

## Run the check

```bash
bash "$(dirname "$0")/verify.sh" <name>    # or a path; omit to verify all
```

`verify.sh` resolves the POC via [`../shared/context.sh`](../shared/context.sh) and
asserts:

| Check | Requirement |
|-------|-------------|
| **Status header** | a `phase:` line with a valid value |
| **Goal** | a non-empty `Goal` section |
| **Implementation** | an `Implementation` section present |
| **Remaining gaps** | a `Remaining gaps` section present |
| **Gap tagging** | every listed gap under Remaining gaps has an id (`G<n>`) and an owner (`[agent]` / `[user]`) |
| **Done consistency** | `ready-to-implement` ⇒ no owned gaps under Remaining gaps |

It prints `PASS` / `FAIL` per file with the specific failing lines, and exits
non-zero if any file fails — so it can gate `/poc implement`.

## When it fails

Report the exact failures and route to `/poc work <name>` (to close/format gaps)
or `/poc create` (if the file is missing required sections entirely). Do not
auto-rewrite the file from `verify` — that is `work`'s job.