poc

Creates Proof of Concept documents validating solution delivery through customer pilots with Go/No-Go recommendations.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill poc-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: poc
Source: https://github.com/Wizarck/nexandro/tree/main/skills/poc
Command: npx skills add https://github.com/Wizarck/nexandro --skill poc-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validating whether a recommended technology stack can actually be delivered to a real customer requires structured pilot planning, measurable success criteria, and evidence-based decisions. This Skill generates POC.md documents that plan and evaluate customer pilots, producing a defensible Go/No-Go/Pivot recommendation. ## Core Features & Use Cases - Pilot Planning: Defines measurable KPIs (technical, operational, customer value), failure thresholds, and weighted scoring models for the pilot. - Evidence-Based Results: Structures results tables with Time-to-Value measurement, structured customer feedback (CSAT, NPS, adoption), and commercial validation via Q2D workflow testing. - Go/No-Go Decision Framework: Produces D-POC-XXX decisions backed by specific evidence, feeding downstream documents like LEAN_BUSINESS_CASE.md and SERVICE_DESIGN.md. - Use Case: After completing a POT (Proof of Technology) for a new offering, use this Skill to plan a 3-site customer pilot, define success KPIs, measure TTV, and produce a Go recommendation for the business case. ## Quick Start Ask the agent to create a POC.md for offering OFFER-XXX based on its completed POT.md, then approve the result and run /qa-poc for validation.

Frequently Asked Questions about poc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Proof of Concept document for a customer pilot?▼

Provide the offering ID and ensure a completed POT.md exists. The agent reads the POT decisions, use cases, and research files, then drafts a POC.md with KPIs, failure thresholds, execution plan, and a Go/No-Go framework for your approval.

What is the difference between POT and POC validation?▼

POT (Proof of Technology) validates the solution stack technically and recommends it via D-POT decisions. POC (Proof of Concept) comes after POT and validates end-to-end delivery to a real customer in a pilot, measuring TTV, adoption, and commercial viability.

Can I run a POC without a completed POT document?▼

A completed POT.md is required because its D-POT-XXX decisions define the POC starting point. If it is missing, the agent asks whether to proceed with an explicit waiver or create the POT first.

How is Time to Value measured in a customer pilot?▼

TTV is measured end-to-end across milestones: Order, Deployment, First Use, and Steady State value delivery. The measured values feed directly into LEAN_BUSINESS_CASE.md adoption and revenue assumptions.

What happens if the POC validation QA fails?▼

After approval, the /qa-poc skill validates the POC.md. If issues are found, the agent fixes them and re-runs QA up to 2 rework cycles; recurring issues or missing source documents are escalated to the user.