Menu
List every POC in .pocs/ with its phase and gap counts (split by [agent]/[user]). Read-only. Use for "/poc list" or "show the pocs".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Archive a done POC out of the active set but keep it as a parity/regression oracle, moving it under .pocs/archive/. Use for "/poc archive <name>" after implementation.
Wipe the .pocs/ directory after confirmation. Use for "/poc clear". Destructive — always confirm and show what will be removed first.
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".
Port a ready-to-implement POC's Implementation section into the product, executing each directive against its acceptance check. Use for "/poc implement <name>" once the POC's gaps are closed.
Delete a single POC file from .pocs/ after confirmation. Use for "/poc remove <name>". Destructive — always confirm first.
POC Driven Development — own a complex feature in one self-contained file under .pocs/, shape it by closing gaps, then implement it into the product. Routes the /poc command surface (create, work, status, list, implement, archive, remove, clear, verify) based on intent. Use when the developer wants to start, shape, inspect, or ship a POC-driven feature.
| name | pocdd-list |
| description | List every POC in .pocs/ with its phase and gap counts (split by [agent]/[user]). Read-only. Use for "/poc list" or "show the pocs". |
| version | 0.1.0 |
| documentation_url | https://github.com/DailybotHQ/pocdd-skill |
| user-invocable | true |
| allowed-tools | Bash, Read, Grep, Glob |
Read-only overview of all POCs. Enumerate with pocdd_list from
../shared/context.sh:
. "$(dirname "$0")/../shared/context.sh"
pocdd_list
For each file, read its header/sections and print a compact table:
| POC | Format | Phase | [agent] gaps | [user] gaps |
|---|
.md reasoned / .py,.js,… runnable).0 / 0 gaps and phase ready-to-implement is ready for
/poc implement..pocs/ is empty or absent, say so and suggest /poc <SOURCE> to start one.Do not modify any file.