poc-spec-driven-builderlisted
Install: claude install-skill th3r-dev/th3-skills
# PoC Spec-Driven Builder
Turns a loosely-described idea into a working, evidence-backed proof of concept — research → spec (SRS) → test matrix → implementation → verification → PR — run end-to-end without interrupting the user for cla~rification. Ambiguity is resolved by making the most reasonable assumption and logging it, not by asking.
This mirrors how modern AI coding agents are meant to work: specs and tests are the source of truth the agent builds *to*, not decisions made ad hoc while writing code. A PoC only proves something if what it's proving was written down first.
Stack-agnostic by design: Step 1 always researches the conventions of whatever language/framework the target repo actually uses (Rust, TypeScript, Python, Go, Dioxus, Next.js, …) — nothing here assumes a particular stack. What's fixed is the *process* (spec → tests → build → ticket → PR), not the technology.
## Core principle: never block on questions
Default behavior for this skill is autonomous execution. When something is unspecified:
1. Pick the most conventional, lowest-risk, industry-standard choice for that domain.
2. Write it into the SRS's **Assumptions** section with a one-line rationale.
3. Keep going.
Only break this rule if the user's message contains an explicit, irreversible constraint that's actually contradictory (e.g., they named two mutually exclusive databases) — then state the conflict plainly and pick one anyway, noting it's an assumption to revisit, rather than stopping.
##