Run a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.
Start a fresh conversation. Replace the highlighted placeholders.
Use poc to run a bounded proof of concept for [selected customer direction and consequential technical assumption], using the provided project context, reality, and terrain to identify the killer assumption, agree a timebox, and define pass/fail criteria before building the minimum required to test it. Return the prototype log with observed evidence and a proceed/pivot/stop/inconclusive result based on the responsible decision-maker's review.
Required inputs
[selected customer direction and consequential technical assumption]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: pocdescription: Run a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.
poc
Purpose
A bounded experiment with evidence and a decision.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.