poc

Generate a time-boxed PoC deliverable with demo scenario and TODO plan.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill poc-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: poc
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/poc
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill poc-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you generate a minimum PoC deliverable that can run in time for customer demos or internal showcases, while producing an explicit, actionable list of technical debt to convert into real implementation later.

Core Features & Use Cases

  • Scope cut for demo viability: Separates what must demo from what can be faked and what can be skipped, so the demo doesn’t fail due to over-scoping.
  • Impact-aware change planning: Checks which existing services/DAOs/controllers/mappers/queries are affected using read/grep-based code inspection before proposing TODOs.
  • Demo scenario + transition to real work: Produces a step-by-step demo script and a /todo-ready plan for converting temporary handling into full implementation.

Quick Start

Tell the AI to create a PoC plan and demo scenario for your use case, optionally referencing input files and the time/deadline constraints.

Frequently Asked Questions about poc

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

FAQPage Schema
How do I plan a PoC demo fast without accumulating untracked technical debt?

To plan a PoC demo fast, you classify scope into Must Demo, Fake OK, and Skip categories, then generate a minimal TODO list with an explicit tech-debt transition plan for later full implementation.

What is code impact analysis and how does it work before writing PoC code?

Code impact analysis identifies affected services, DAOs, controllers, and mappers by running Read, Glob, and Grep inspections on relevant code and docs before proposing any temporary PoC implementation.

How do I scope cut a customer demo to ensure only critical success criteria are built?

Scope cutting for a customer demo involves separating features that must demo from those you can fake or skip, preventing demo failure from over-scoping while proving the critical success criterion quickly.

How do I transition temporary PoC handling into a real implementation plan?

Transition temporary PoC handling by generating a /todo-ready plan that converts temporary code into full implementation, mapping out the specific technical debt items accumulated during the time-boxed validation.

Does generating a PoC deliverable require any specific external dependencies or frameworks?

Generating a PoC deliverable requires no external dependencies, relying solely on built-in Read, Glob, and Grep tools to perform impact checks and apply PoC-safe conventions for temporary versus real implementation guidance.

When should I avoid using a time-boxed PoC approach for feature validation?

Avoid a time-boxed PoC approach when a customer demo or internal walkthrough does not require proving a critical success criterion quickly, or when overbuilding is not a risk and full immediate implementation is viable.