ワンクリックで
pocdd-remove
Delete a single POC file from .pocs/ after confirmation. Use for "/poc remove <name>". Destructive — always confirm first.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Delete a single POC file from .pocs/ after confirmation. Use for "/poc remove <name>". Destructive — always confirm first.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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".
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-remove |
| description | Delete a single POC file from .pocs/ after confirmation. Use for "/poc remove <name>". Destructive — always confirm first. |
| version | 0.1.0 |
| documentation_url | https://github.com/DailybotHQ/pocdd-skill |
| user-invocable | true |
| allowed-tools | Bash, Read, Glob |
Delete one POC. Resolve it with pocdd_resolve <name> from
../shared/context.sh.
pocdd_list.rm -i "$(pocdd_resolve <name>)"
.pocs/.<name>_token.json,
__pycache__), mention it and offer to remove it too — but never delete
credentials without saying so.Prefer /poc archive <name> when the POC still has signal. Use remove only
when it duplicated the product 1:1 with nothing extra to offer.