# Pocdd Create

> Create a new POC-driven feature file under .pocs/ from any source (a sentence, an issue, a document, a URL). Picks the file format by risk, writes the Goal, and seeds Remaining gaps including a failure-mode sweep. Use for "/poc <SOURCE>" or "start a POC for X".

- Skill: `dailybothq/pocdd-create` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dailybothq/pocdd-create`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dailybothq/pocdd-create/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-create

---


# POCDD — Create

Bootstrap one self-contained POC file from a **SOURCE**. First read
[`../shared/conventions.md`](../shared/conventions.md).

Configured languages for this install: **python,md**

## Inputs

`SOURCE` is anything that defines the goal: a one-line sentence, an issue id/link,
a path to a document, or a provider URL. (`/poc create <SOURCE>` and bare
`/poc <SOURCE>` both arrive here.)

## Procedure

1. **Gather context from the SOURCE.** Read the file, fetch the URL, or read the
   issue. Distil it into a single **Goal** statement. If the source is just a
   sentence, use it verbatim as the goal.
2. **Choose the format by risk** (see conventions):
   - *Unknown external/runtime behavior* (API, OAuth, sync, time zones) →
     **runnable** file from the templates that match this install:
     - Python: copy [`../templates/poc.py`](../templates/poc.py)
     - Markdown: copy [`../templates/poc.md`](../templates/poc.md)
   - *Internal/domain complexity* (refactor, wiring, product rules) → **`.md`**
     when available in this install.
   - When in doubt, prefer the runnable form if there is *any* external system to
     probe; otherwise `.md`.
3. **Name it by domain** — short `kebab`/`snake` name (e.g. `calendar`,
   `holidays-sync`). Never `test`.
4. **Resolve and create `.pocs/`** via [`../shared/context.sh`](../shared/context.sh)
   (`pocdd_ensure_dir`).
5. **Write the file** from the chosen template into `.pocs/<name>.<ext>`, filling
   the **Goal** section and setting the header `phase: spike`.
6. **Seed Remaining gaps — the highest-value step.** Enumerate what must be
   *proven*, *decided*, or *handled* to reach the goal. Tag each `[agent]` or
   `[user]`, give stable ids `G1…`. **Always run the failure-mode sweep** for
   anything external (auth/token refresh, pagination, rate limits, partial
   failures, retries/idempotency, malformed data, time zones).
7. **Report**: the file path, format chosen (and why), and the seeded gap list
   split by owner. Suggest `/poc work <name>` next (at most **2**
   `[agent]` gaps close per work pass on this install).

## Guardrails

- Never write outside `.pocs/`. Never commit `.pocs/`.
- Reference codebase by path; do not paste production code into the file.
- Do not invent product decisions — log them as `[user]` gaps.