--- name: project-primer description: > Creates a pre-kickoff project primer for a Benmore Technologies client engagement. Use when preparing to meet a new client for the first time — before the kickoff call. Triggered by phrases like "create a primer", "write a primer for project", "pre-kickoff primer", "client primer", or "prepare a primer for [client/project]". Gathers sales team notes, researches the client's industry and market (with cited sources), incorporates the user's complexity thoughts and value proposition hypotheses, writes a structured PRIMER.md in the project's Discovery directory, then generates a polished PRIMER_PRESENTATION.html using the embedded design system below. context: fork --- # Project Primer Produces two files before a client kickoff call: 1. `Active_Projects/[ProjectDir]/Discovery/PRIMER.md` — structured markdown document 2. `Active_Projects/[ProjectDir]/Discovery/PRIMER_PRESENTATION.html` — polished visual presentation --- ## Workflow ### Step 1 — Gather Inputs Ask in a **single message** for anything not already provided: - **Project directory** — e.g., `174-DrewLauten` - **Sales team notes** — emails, call notes, Slack summaries, description of the client's idea - **Supporting docs** — prototype links, decks, anything the client shared (optional) - **Your complexity thoughts** — hypotheses on value props, pain points, open questions to hash out at kickoff Do not ask for information already in the conversation. Do not ask questions one at a time. ### Step 2 — Identify Industry & Market From the notes, extract: - The **industry** (e.g., vacation rentals, fintech, legal tech, healthcare) - The **specific market segment** (e.g., short-term rental operators, solo attorneys) - **Adjacent markets** the product touches ### Step 3 — Research the Market Use WebSearch to find **current, cited data**. Run at least 3–5 searches across: | Area | What to find | | ---------------- | ----------------------------------------------------------- | | Market size | Global + US value, year, CAGR, projected value + year | | Trends | Key tailwinds driving the market right now | | Pain points | Industry surveys, operator reports, documented frustrations | | Competitors | Analogous platforms — name, founding year, focus, pricing | | User motivations | Behavioural data on the target user | Cite every statistic with an inline markdown link `([Source Name](url))`. Do not fabricate numbers. Prioritize: industry reports (Fortune Business Insights, Mordor Intelligence, Statista, IBISWorld), government data (BLS, Census), credible trade publications. ### Step 4 — Write PRIMER.md Save to: `Active_Projects/[ProjectDir]/Discovery/PRIMER.md` Follow this exact structure: ``` # [Product Name] — Pre-Kickoff Project Primer **Prepared by:** Benmore Technologies **Date:** [Today's date] **Client:** [Client full name] **Project Code:** BEN-[XXX] --- ## What We Understand You're Building [2–4 paragraphs. Plain language. Explain the product, who it's for, and the core value exchange. Describe the core loop as a numbered list of 3–5 steps. Write so the client reads it and nods. No jargon. No bullets in the opening paragraphs.] From [prototype / our conversation / the materials you shared], we can see the core loop clearly: 1. **[Actor 1]** [action + what they provide/get] 2. **[Actor 2]** [action + what they provide/get] 3. [Continue through full cycle] --- ## Industry & Market Context ### [Primary Market Name] [Product] sits at the intersection of [N] markets, each with significant tailwinds. **[Market 1]** [Stats with inline citations.] ([Source](url)) **[Market 2]** [Stats with inline citations.] ([Source](url)) **[Market 3]** [Stats with inline citations.] ([Source](url)) ### [Secondary Theme — e.g. user motivations, operator pain point] [2–3 paragraphs on user-side context with citations.] ### Existing [Alternatives / Competitors / Analogous Platforms] [1–2 framing sentences.] | Platform | Founded | Focus | Pricing | |----------|---------|-------|---------| | **[Name]** | [Year] | [Description] | [Price] | **The key gap these platforms leave:** [What none of them do that this product would do.] This is [Client Name]'s opportunity. --- ## What We Think the Core Value Propositions Are ### For [User Type 1] - **[Benefit]** — [1-sentence explanation] - **[Benefit]** — [1-sentence explanation] ### For [User Type 2] - **[Benefit]** — [1-sentence explanation] - **[Benefit]** — [1-sentence explanation] --- ## Open Questions We Want to Discuss With You [Intro sentence about using the kickoff call to align before scoping.] ### Tier 1 — Core Functionality Decisions **1. [Question title]** [Context + options + why it matters for scope.] - [Option A] - [Option B] [Continue for 4–6 Tier 1 questions drawn from the user's complexity thoughts.] ### Tier 2 — Complexity & Scope Decisions **[N]. [Question title]** [Same pattern. 2–4 questions.] --- ## Our Initial Read on Complexity [1–2 sentences characterising the product type and core design challenge.] [Bullet list of 4–6 design dimensions that will shape timeline and cost.] None of these are blockers — they're design decisions. But they'll significantly shape timeline and cost. --- ## What We'd Like to Accomplish in Our Kickoff Call 1. [Goal] 2. [Goal] 3. [Goal] 4. [Goal] 5. [Goal] --- ## Next Steps from Benmore's Side After our kickoff call, we'll produce: - [ ] Technical Requirements Document - [ ] MVP Features List (with clear in/out of scope line) - [ ] User Flow Diagrams ([actor 1] journey + [actor 2] journey) - [ ] Quote, Associated Fees & Timeline [1–2 closing sentences on what's compelling about the opportunity.] --- *Prepared by Benmore Technologies — [benmoretechnologies.com](https://benmoretechnologies.com)* *Technical Lead: Aditya Niture* ``` Writing rules: - Confident, clear, no jargon — written for the client, not internal use - All stats cited inline - Open questions drawn from the user's complexity thoughts (Step 1), not generic filler ### Step 5 — Generate HTML Presentation After writing PRIMER.md, generate `PRIMER_PRESENTATION.html` in the same directory using the design system below. The HTML must be fully self-contained (no external dependencies except Google Fonts and CDN-hosted Mermaid/Chart.js). --- ## HTML Design System Use this design system to turn the PRIMER.md into a polished one-pager. ### Visual Identity Dark navy glassmorphism. Multi-tone navy gradient background, color-coded content cards, subtle glow accents. No emojis — use `→` and `•` only. ### Color Palette | Element | Value | | ----------------- | ------------------------------------------------------------------------------------------ | | Background | `linear-gradient(135deg, #0a1628 0%, #1a2744 25%, #0f2d4a 50%, #1a3a5c 75%, #0d1a2d 100%)` | | Primary text | `#ffffff` | | Secondary text | `rgba(255,255,255,0.85)` | | Muted text | `rgba(255,255,255,0.5)` | | Accent blue | `#60a5fa` | | Accent blue light | `#93c5fd` | | Success green | `#34d399` | | Warning amber | `#fbbf24` | | Error red | `#f87171` | | Special purple | `#a78bfa` | | Card background | `linear-gradient(135deg, rgba(255,255,255,0.05) 0%, rgba(255,255,255,0.02) 100%)` | | Card border | `rgba(255,255,255,0.08)` | ### Typography - Font: `'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif` - H1: 2.75rem, 700, gradient text fill, letter-spacing -0.02em - Section headers: 0.85rem, 600, uppercase, letter-spacing 0.1em, accent blue - Card headers: 1.15rem, 600, color varies by card type - Body: 1rem, 400, line-height 1.7 ### Card Type Rules Select card type automatically based on content: | Card Class | Color | Use When | | ----------------- | ------------------------- | ------------------------------------------------ | | `.card` | Blue | General info, descriptions, default | | `.feature-card` | Green | Features, benefits, capabilities, deliverables | | `.warning-card` | Amber | Warnings, requirements, important notes | | `.error-card` | Red | Risks, blockers, critical issues, what NOT to do | | `.special-card` | Purple | Future features, AI, roadmap, advanced topics | | `.highlight-card` | Blue accent + left border | Key takeaways, summaries, TL;DR | | `.role-card` | Blue tinted + badge | People, roles, user types, personas | ### HTML Template ```html [Document Title]
``` When generating the HTML, replace the comment block with real sections and populated cards drawn directly from the PRIMER.md content. Every section of the markdown maps to HTML sections and appropriately typed cards. --- ## Output Confirm both files to the user when complete: | File | Path | | -------------------------- | ------------------------------------------------------------------- | | `PRIMER.md` | `Active_Projects/XXX-ClientName/Discovery/PRIMER.md` | | `PRIMER_PRESENTATION.html` | `Active_Projects/XXX-ClientName/Discovery/PRIMER_PRESENTATION.html` |