ti-founder
starsforks
How to install ti-founder?
eph5xx/tweakidea/ti-founder
$npx -y skills add eph5xx/tweakidea --skill ti-founderFounder profile template, creation questions, section definitions, and fit question guidance for TweakIdea evaluations
SKILL.md
| 1 | Reference data for all founder profile operations. The orchestrator (`evaluate.md`) uses this skill to create, read, and update `FOUNDER.md` at `~/.tweakidea/FOUNDER.md`. |
| 2 | |
| 3 | --- |
| 4 | |
| 5 | ## FOUNDER.md Template |
| 6 | |
| 7 | ``` |
| 8 | # Founder Profile |
| 9 | |
| 10 | ## Expertise & Domain Knowledge |
| 11 | - Domain: [domain/industry] |
| 12 | - Depth: [depth/level] |
| 13 | - Insight: [unique perspective] |
| 14 | |
| 15 | ## Relevant Experience |
| 16 | - Role: [most relevant role] |
| 17 | - Achievement: [relevant accomplishment] |
| 18 | - Duration: [time in space] |
| 19 | |
| 20 | ## Network & Market Access |
| 21 | - Connections: [network] |
| 22 | - Channel: [customer access] |
| 23 | - Capital: [resources/funding] |
| 24 | |
| 25 | ## Build Capabilities |
| 26 | - Technical: [build capability] |
| 27 | - Team: [team composition] |
| 28 | - Speed: [shipping ability] |
| 29 | |
| 30 | ## Drive & Commitment |
| 31 | - Motivation: [why this problem] |
| 32 | - Experience: [personal connection] |
| 33 | - Commitment: [commitment level] |
| 34 | |
| 35 | --- |
| 36 | *Created: [date] | Last updated: [date]* |
| 37 | ``` |
| 38 | |
| 39 | ### Template Rules |
| 40 | |
| 41 | - Field names (Domain, Depth, Insight, etc.) are starter suggestions. Use whatever tagged entries naturally emerge from the founder's answers. |
| 42 | - Not every section needs all suggested fields -- some may have 1 entry, some may have 5. |
| 43 | - Keep FOUNDER.md under 100 lines (context budget). |
| 44 | - Do NOT add new sections beyond the 5 defined above. Fit additional information into the most relevant existing section as tagged list entries (e.g., `- Key: Value`). |
| 45 | |
| 46 | --- |
| 47 | |
| 48 | ## Profile Creation Questions |
| 49 | |
| 50 | Ask these 5 questions one at a time using AskUserQuestion, waiting for each answer before proceeding to the next: |
| 51 | |
| 52 | | # | Question | Maps to Section | |
| 53 | |---|----------|-----------------| |
| 54 | | 1 | "What's your professional background? (Industry experience, roles, education)" | Relevant Experience | |
| 55 | | 2 | "What domains do you have deep expertise in?" | Expertise & Domain Knowledge | |
| 56 | | 3 | "What relevant network or resources do you have? (Connections, advisors, potential early customers, capital access)" | Network & Market Access | |
| 57 | | 4 | "What can you or your team build? (Technical strengths, capabilities)" | Build Capabilities | |
| 58 | | 5 | "What drives you to work on hard problems? (Personal motivation, what keeps you going)" | Drive & Commitment | |
| 59 | |
| 60 | Preamble before asking: "I don't have a founder profile yet. I'll ask a few quick questions to understand your background -- this helps evaluate founder-market fit and only needs to happen once." |
| 61 | |
| 62 | If during the questioning flow the user volunteers additional relevant information beyond what was asked, capture it in the appropriate section. Do not add new sections. |
| 63 | |
| 64 | --- |
| 65 | |
| 66 | ## Fit Question Guidance |
| 67 | |
| 68 | After profile creation/load, ask 2-4 questions about the founder's connection to THIS specific idea. These questions serve a dual purpose: surface persistent founder attributes while assessing idea-specific fit. |
| 69 | |
| 70 | ### Design Principle |
| 71 | |
| 72 | Each question must simultaneously: |
| 73 | 1. Surface a **persistent founder attribute** (expertise, experience, network, capability) that would appear in FOUNDER.md |
| 74 | 2. Assess **idea-specific fit** by anchoring that attribute to the current idea domain |
| 75 | |
| 76 | Do NOT write questions that are purely idea-specific ("How big is this market?") or purely background ("What's your experience?"). The profile creation questions already captured generic background. Fit questions contextualize those attributes to this idea. |
| 77 | |
| 78 | ### Focus |
| 79 | |
| 80 | Founder-idea fit exclusively -- NOT generic idea questions. Do not ask about target customers, market size, competitors, or other idea details already present in the idea text. |
| 81 | |
| 82 | ### Dynamic Generation |
| 83 | |
| 84 | Questions must be generated based on: |
| 85 | - The idea domain (what industry/problem space is described) |
| 86 | - What FOUNDER.md already covers -- do NOT re-ask what is already known |
| 87 | - Gaps in understanding the founder-idea connection that would help evaluate founder-market fit |
| 88 | |
| 89 | ### Example Dual-Purpose Patterns |
| 90 | |
| 91 | Adapt to the specific idea -- do not use these verbatim if they don't fit: |
| 92 | - "What experience or expertise gives you an edge in [the idea's specific domain]?" -- surfaces expertise (persistent) + idea relevance |
| 93 | - "Have you personally experienced [the specific problem], and what was your situation?" -- surfaces personal connection (persistent) + idea validation |
| 94 | - "Do you have existing relationships with [target segment], and how strong is that access?" -- surfaces network (persistent) + idea-specific channel |
| 95 | - "What have you already built or shipped that's relevant to [this problem area]?" -- surfaces build capability (persistent) + idea relevance |
| 96 | |
| 97 | ### Presentation |
| 98 | |
| 99 | Present all 2-4 fit questions in a **single AskUserQuestion call** so the founder sees and answers all questions together in one interaction. Do NOT preview questions first, do NOT ask them one at a time. One call, all questions. |
| 100 | |
| 101 | For each question, provide 2-4 answer options relevant to the question type (e.g., depth-of-experience options, yes/no with elaboration, etc.) |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
