nocoder26
- 13 skills
- 0 followers
- 11 hours ago last updated
- ▌ Why · nocoder26Capture or recall the founder's motivation. Two modes — initial capture (5 questions), or recall mode when the founder is about to quit, pivot, or stop doing the work. Surfaces their own past words back at them.
- ▌ Pitch · nocoder26Render brain/story.md into a 10-slide pitch deck where every claim cites a brain entry. Refuses to fabricate TAM, vanity metrics, or unsupported quotes. Flags weak slides honestly so the founder fixes them before any VC sees the deck.
- ▌ Pivot · nocoder26Walk through the 10 canonical pivot types using brain evidence to inform direction. Forces explicit kill criteria for the previous hypothesis before allowing a pivot. Logs to brain/pivots.md with full reasoning.
- ▌ Start · nocoder26First-run concierge. Walks a new founder from zero to a captured hypothesis and a real interview script in ~10 minutes. Auto-creates the brain/ skeleton, runs /why → /problem → /interview in sequence with one-line explanations of why each step matters. Use this as the front door instead of running individual skills.
- ▌ Story · nocoder26Construct the founder's narrative arc — origin, why-you, journey, vision, ask. Reads brain/why.md and brain/ for cited evidence. Output feeds /pitch downstream. Every claim cites a brain entry.
- ▌ Gbrain · nocoder26Optional bridge — sync Telos's brain/ folder into a gbrain MCP instance so interviews, believers, decisions, and pivots become queryable, linked, and citable across projects. Telos works perfectly without this; gbrain integration is purely additive. Hard-refuses if gbrain MCP is not detected. Idempotent, never silently overwrites, requires explicit opt-in per category, leaves an audit trail in brain/integrations/gbrain-log.md.
- ▌ Problem · nocoder26Capture or refine the founder's problem hypothesis with Mom-Test rigor. Use at Stage 0 initial setup, or when interview signals contradict the current hypothesis.
- ▌ Roleplay · nocoder26Practice an interview script against a deliberately adversarial AI customer who pushes back, demands specifics, and refuses to validate vague claims. Outputs to brain/practice/ (separate namespace from real interviews). Pre-flight requires at least 1 real interview to prevent roleplay-as-substitute. The point is to surface bad questions before they waste a real customer call — never to substitute for talking to humans.
- ▌ Believers · nocoder26Classify interview participants as Believer / Neutral / Infidel using the earlyvangelist test. Track believer density. Surface PMF-mirage when too many users are tire-kickers.
- ▌ Interview · nocoder26Generate a discipline-driven customer interview script from the current problem hypothesis. After the interview, extract atomic signals (verbatim quotes, observed behaviors) into the brain.
- ▌ Pmf Check · nocoder26Triangulate Product-Market Fit signal from three independent sources — disappointment survey, retention cohorts, believer density. Returns Strong PMF / PMF / Pre-PMF / PMF Mirage. The triangulation is what's hard to fake.
- ▌ Build Check · nocoder26Before adding a feature, query brain/evidence/ for matching customer signals. Returns GREEN (clear evidence), AMBER (related signal), or RED (no evidence). Use before any non-trivial product change.
- ▌ Default Alive · nocoder26Calculate runway, growth rate, and default alive vs default dead status. Required before any new spend or hire. Surfaces the brutal math founders avoid.