From FOUNDRY — Value-Flow Production System
The FOUNDER method — how a software production house turns an idea into a product one vertical slice at a time through value-stations and value-handlers, governed by a five-level performance-instrumented test contract. Use when planning the production line, defining stages and their owners, onboarding a new value-handler agent, or explaining WHAT is being built and HOW. Trigger phrases: "founder method", "value stations", "who owns this stage", "production line", "how does our process work".
How this skill is triggered — by the user, by Claude, or both
Slash command
/foundry:founder-methodThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A method for running an application-layer production house. It exists to make every change
A method for running an application-layer production house. It exists to make every change rigorously disciplined: each increment passes through a fixed line of stations, each station has a defined value, an owning handler, and an exit gate, and nothing merges that has not satisfied the test contract.
FOUNDER_COO).| Station | Value (what it adds) | Handler | Exit gate |
|---|---|---|---|
| IDEA | a candidate worth pursuing | founder | thesis stated; stack-fit argued |
| VALIDATE | evidence a buyer exists | marketer | ≥3/10 target users say "I'd pay" |
| SPEC | unambiguous, agent-readable intent | roadmapper | EARS + .feature + acceptance criteria |
| DESIGN | surfaces a human can use | frontend | INTENT-marked screens; a11y + privacy held |
| SLICE | working code + tests | builder | unit+module green; one-way deps intact |
| HARDEN | correctness + safety | reviewer, security-auditor | both APPROVE; boundary/system green |
| SHIP | product in users' hands | founder | STORY green; perf-delta gate passed; deployed |
| LEARN | the next IDEA | marketer | signal captured; positioning still cohesive |
LEARN feeds IDEA. The loop is the product.
Five levels, each performance-instrumented:
FOUNDER verifies this contract on every invocation and halts (CONTRACT UNMET) if any
level, instrument, or the STORY gate is missing.
foundry -help (project ./.claude, or the user's global config if present): learn the stage list and,
per stage, what to put in for a rich and viable result out.frontend -help: learn the surface taxonomy (Capture/Display/Navigate/Instrument), the
INTENT marker protocol, and the two non-negotiables (a11y floor, privacy-as-architecture).references/readout-template.md).Every station MUST have a handler. An unstaffed station is a defect FOUNDER reports; it
nominates an existing agent or recommends authoring one via skill-creator. No station
without a handler; no gate without a check; no merge without the contract.
See references/station-contracts.md for the precise per-station input/exit definitions
(this is the same material the value-station-handoff skill serves to gate-keepers).
npx claudepluginhub agentic-underground/idea-to-productionProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.