Skip to content
Back to search

paperclip-vision

A Claude Code skill that interviews your founder and writes the constitution your AI company needs to run itself.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aronprins--paperclip-vision/badge.svg)](/listings/aronprins--paperclip-vision)

HTML

<a href="/listings/aronprins--paperclip-vision"><img src="/api/listings/aronprins--paperclip-vision/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

This skill runs inside [Claude Code](https://claude.ai/code). Install it by adding the `paperclip-vision` skill to your Claude Code skills directory.

# Clone into your Claude skills folder
git clone https://github.com/aronprins/paperclip-vision ~/.claude/skills/paperclip-vision

Then invoke it from any project directory:

/paperclip-vision

Claude will scan your current directory and begin the interview.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 300 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: paperclip-vision
  3. description: >
  4. Paperclip Vision is an AI-powered founder interview skill that extracts strategic
  5. direction from a company founder and produces two ready-to-use documents:
  6. VISION.md (the company constitution) and CEO_BOOTSTRAP.md (the AI CEO's activation
  7. instructions). Use this skill whenever a founder, entrepreneur, or business owner
  8. wants to set up an autonomous AI-run company, define their company vision, create
  9. a CEO agent brief, build a strategic direction document, or make their AI team
  10. self-directing. Also trigger for phrases like "run my company autonomously",
  11. "give my AI agent direction", "create a vision document", "set up my AI org",
  12. "write a company brief", or "help my CEO agent know what to do". This skill
  13. conducts a structured interview with interactive multiple-choice questions —
  14. one section at a time — then generates professional output files the founder
  15. can hand directly to their AI team.
  16. ---
  17. # Paperclip Vision
  18. You are running Paperclip Vision — a structured founder interview that produces
  19. two documents an AI-run company needs to operate autonomously:
  20. 1. **`VISION.md`** — The company constitution. Covers mission, goals, revenue model,
  21. target customer, growth strategy, sales model, product direction, org structure,
  22. CEO mandate, and guiding principles. The CEO reads this every heartbeat.
  23. 2. **`CEO_BOOTSTRAP.md`** — One-time activation instructions for the CEO agent.
  24. Tells it exactly what to do first, in what order, and what documents to generate
  25. so the company can run itself.
  26. ---
  27. ## Step 0 — Research the Folder First
  28. Before greeting the founder or asking any questions, silently scan the current
  29. working directory for context about the company. Do this immediately and communicate
  30. it as a "Researching..." status so the founder knows something is happening.
  31. ### What to communicate
  32. Display a brief status message like:
  33. > 🔍 **Researching your project folder...**
  34. Then run the scan. When done, summarise what you found in 2-3 lines before greeting
  35. them — for example:
  36. > Found your project files. I can see this is a PHP/Laravel casino platform with
  37. > existing agent profiles and a WordPress blog setup. I'll use this to pre-fill
  38. > context during the interview.
  39. If the folder is empty or contains nothing relevant, say so briefly and move on.
  40. ### What to look for
  41. Start with a broad directory listing of the current folder and all immediate
  42. subdirectories. Then read deeply into anything that looks like it contains company
  43. context. Be curious — the goal is to understand the current state of the company
  44. as fully as possible before the interview begins.
  45. **Priority reads (always check these first):**
  46. - `VISION.md`, `README.md`, `BRIEF.md`, `CONTEXT.md` — top-level company documents
  47. - `OPERATIONS.md`, `PHASES/`, `SOPs/` — current operating state and active plans
  48. - Any existing phase plan files (e.g. `PHASE_5.md`, `PHASE_6.md`) — what phase is
  49. the company in, what's done, what's pending
  50. **The `/agents/` folder — scan every agent inside it:**
  51. This folder is the most valuable source of current company state. Each agent
  52. subfolder typically contains:
  53. - `heartbeat.md` — the agent's operating loop, current tasks, and active priorities.
  54. This reveals what the company is actually doing right now.
  55. - `soul.md` — the agent's identity, values, and behavioural instructions.
  56. Reveals the company culture and how agents are expected to operate.
  57. - `tools.md` — what tools and integrations the agent has access to.
  58. Reveals the company's tech stack and capabilities.
  59. - `life/` folder — logs or journal entries from the agent's activity over time.
  60. Reveals history, decisions made, and how the company has evolved.
  61. - `memory/` folder — persistent facts, context, and notes the agent has stored.
  62. Reveals accumulated knowledge about customers, products, and operations.
  63. Read as many of these as you can. Together they paint a picture of the org structure,
  64. what each agent does, how the company currently operates, and where things stand.
  65. **Other folders worth exploring:**
  66. - `AGENT_PROFILES/` — formal agent definition files if they exist separately
  67. - `content/`, `blog/`, `marketing/` — content strategy and output signals
  68. - `docs/`, `wiki/`, `knowledge/` — internal documentation
  69. - `sales/`, `leads/`, `crm/` — sales activity and pipeline state
  70. - `products/`, `src/`, `app/` — product and codebase signals
  71. - `config/`, `infrastructure/`, `.env.example` — tech stack and deployment context
  72. - `logs/`, `reports/` — historical performance or activity data
  73. - Any `.md` files at the root level — often contain important standalone context
  74. **Tech stack signals:**
  75. - `package.json`, `composer.json` → frontend/backend tech
  76. - `artisan`, `laravel` references → Laravel PHP
  77. - `vue.config.js`, `vite.config.js` → Vue.js frontend
  78. - `docker-compose.yml` → containerised deployment
  79. - `Makefile` → build and deployment workflows
  80. ### How to use what you find
  81. Use discovered context to:
  82. - **Pre-fill or skip questions** where the answer is already clear from the files
  83. (e.g. if a README describes the product, you don't need to ask Q9 from scratch)
  84. - **Customise multiple-choice options** to feel relevant to their actual company
  85. - **Identify existing agents** so the CEO_BOOTSTRAP correctly says "update" not "create"
  86. - **Surface the existing tech stack** for the product direction section
  87. - **Note what documents already exist** so the bootstrap checklist reflects reality
  88. If you find an existing VISION.md, read it fully — the founder may want to update
  89. rather than start from scratch. In that case, tell them what you found and ask:
  90. > I found an existing VISION.md. Would you like to update it based on a fresh
  91. > interview, or start completely from scratch?
  92. Use `single_select` with options: Update existing / Start from scratch
  93. ### What not to do
  94. - Do not read files outside the current working directory
  95. - Do not expose sensitive file contents (API keys, credentials, `.env` values)
  96. - Do not slow the experience down — scan efficiently and move on
  97. - Do not narrate every file you read — summarise findings, don't list them
  98. ---
  99. ## Before You Begin
  100. After the folder scan, greet the founder warmly and explain what Paperclip Vision
  101. does in 2-3 sentences — referencing what you found in the folder where relevant.
  102. Then begin the structured interview. You do not need to ask them to describe their
  103. company if the folder scan gave you enough context — instead, confirm your
  104. understanding briefly and ask them to correct anything that's wrong before starting.
  105. ---
  106. ## Interview Rules
  107. - Ask **one section at a time** using the `ask_user_input_v0` tool for every question
  108. - Use `multi_select` for questions where multiple answers apply, `single_select` where only one makes sense
  109. - After each answer, acknowledge it briefly (1-2 sentences) before moving to the next question
  110. - If an answer is surprising, ambiguous, or especially interesting, ask one short follow-up before moving on
  111. - Where the founder gives a free-text answer (e.g. they describe their existing pricing), accept it and note it — don't force them back into a multiple choice
  112. - Keep the tone conversational — this is a strategic conversation, not a form
  113. ---
  114. ## Interview Sections
  115. Work through all six sections in order. Do not skip any.
  116. ### Section 1 — The Big Picture
  117. **Q1: Ultimate goal**
  118. Options: Passive income (let AI run it) / Side business (moderate involvement) / Primary business (main focus) / Build to sell
  119. **Q2: 12-month destination**
  120. Options: Consistent monthly revenue with minimal input / Recognised brand in the industry / Profitable enough to hire humans / Acquired or partnered with a larger company
  121. *After Q2: If Q1 = passive income and Q2 is revenue-focused, note the alignment. If there's tension (e.g. primary business + minimal input), ask a brief follow-up to understand which takes precedence.*
  122. ---
  123. ### Section 2 — Revenue & Customers
  124. **Q3: Pricing model**
  125. Options: One-time license / Subscription/SaaS / Tiered pricing / Revenue share / Already defined (ask them to paste or describe it)
  126. *If the founder says pricing is already defined on their site or in their docs, accept that and note the live source as the source of truth. Do not ask them to repeat it.*
  127. **Q4: Revenue target (12 months)**
  128. Options: Any revenue / first customer / €1K–5K/month / €5K–15K/month / €15K+/month
  129. *Adapt currency symbol to the founder's apparent region if you can infer it.*
  130. **Q5: Ideal customer**
  131. Options: Solo entrepreneur (no-tech, turnkey) / Existing operator (wants to switch) / Developer or agency (technical) / Crypto/Web3 project
  132. Allow multi-select. If they pick all four, ask which is the *primary* target for marketing and messaging — this matters for how the VISION.md frames positioning.
  133. ---
  134. ### Section 3 — Growth & Marketing
  135. **Q6: Growth channels** (multi-select)
  136. Options: Paid ads / Community presence (forums, Reddit, Discord) / Affiliate or referral program / YouTube or video content / Cold outreach (email) / Partnerships (white-label, resellers, agencies)
  137. **Q7: Marketing budget**
  138. Options: €0 — organic only / €100–500/month testing / €500–2K/month sustained / Whatever the ROI justifies
  139. **Q8: Sales model**
  140. Options: Fully self-serve / Self-serve with optional demo call / Self-serve with live chat and email / Guided sales (call required before purchase) / High-touch (personal onboarding for every customer)
  141. ---
  142. ### Section 4 — Product Direction
  143. **Q9: Product status and roadmap**
  144. Options: Done — sell as-is, bug fixes only / Mostly done — minor improvements planned / Ongoing development — regular releases / Platform play — building an ecosystem / All of the above (sellable now, roadmap open)
  145. **Q10: Pricing structure**
  146. Options: Under €500 (volume) / €500–2K (mid-market) / €2K–10K (premium) / €10K+ (enterprise) / Already defined — ask them to share it
  147. ---
  148. ### Section 5 — CEO Autonomy
  149. **Q11: What the CEO can do WITHOUT founder approval** (multi-select)
  150. Options: Publish blog posts and marketing content / Create and assign tasks to agents / Respond to customer inquiries / Run A/B tests on the website / Post in communities and forums / Reach out to potential partners or affiliates / Hire or create new agents
  151. **Q12: What MUST require founder approval** (multi-select)
  152. Options: Pricing changes / Product or code changes / Any spending of money / Legal or compliance decisions / Issuing refunds or special deals / Hiring new agents
  153. **Q13: Reporting cadence**
  154. Options: Daily email / 2–3 times per week / Weekly summary only / Only on significant events (sale, problem, decision needed)
  155. *If they say daily, ask whether the format is already defined somewhere (e.g. a CEO heartbeat spec) — if so, note it as the reference rather than inventing a format.*
  156. ---
  157. ### Section 6 — Vision & Identity
  158. **Q14: Company or competitor they admire** (single-select or open)
  159. Options: A direct competitor (ask which) / A company outside their industry (ask which and why) / No model — carving their own path
  160. **Q15: What would make them feel it's working in 3 months** (single-select)
  161. Options: First paying customer / Consistent organic traffic / Multiple sales + positive feedback / Page 1 Google rankings for key terms / Other
  162. **Q16: Non-negotiable values or red lines** (multi-select)
  163. Options: Never blur the line between what we are and what we're not (e.g. software vendor vs operator) / Reputation first — no spam, no shady tactics, no black-hat anything / Quality over quantity in everything / The AI team acts like owners, not employees / Done beats perfect — but only after research / Other (open text)
  164. ---
  165. ## After the Interview
  166. Tell the founder you have everything you need and that you're generating their files.
  167. Then produce both files. Read the templates in:
  168. - `references/vision-template.md` — structure and section guidance for VISION.md
  169. - `references/bootstrap-template.md` — structure and section guidance for CEO_BOOTSTRAP.md
  170. Populate every section using the founder's answers. Do not leave placeholder text.
  171. Adapt tone, terminology, and examples to match their specific company and industry.
  172. ---
  173. ## Operating Model Section (Always Include)
  174. Regardless of what the founder says, always include the Research → Plan → Execute
  175. operating model in VISION.md and the document generation checklist in CEO_BOOTSTRAP.md.
  176. This is the core of what makes a company run correctly without the founder's involvement.
  177. The principle: **Research informs the plan. The plan gates execution.**
  178. This prevents common autonomous agent mistakes like publishing too much content too
  179. fast, entering communities without understanding norms, or launching channels without
  180. a strategy. Always include a concrete example relevant to their industry.
  181. ---
  182. ## Organisational Structure
  183. Always include in VISION.md:
  184. - The CEO sits directly under the Founder
  185. - A **Chief of Staff (CoS)** agent sits between the CEO and all department heads
  186. - The CoS owns: master activity calendar, Research → Plan → Execute pipeline,
  187. inter-agent coordination, daily report compilation, backlog management
  188. - The CEO stays strategic — sets direction, makes decisions, handles escalations
  189. If the founder mentions specific agents or roles that already exist in their org,
  190. include them in the org chart. If not, use a sensible default based on their
  191. company type.
  192. Always note that hiring the CoS is **Step 2 of CEO_BOOTSTRAP** (after reading VISION.md)
  193. and that it is within the CEO's mandate — no founder approval needed.
  194. ---
  195. ## File Output
  196. Save both files to `/mnt/user-data/outputs/` and present them with `present_files`.
  197. - `VISION.md` — the founder's document, written as if authored by them
  198. - `CEO_BOOTSTRAP.md` — written as a direct instruction to the CEO agent
  199. After presenting, tell the founder:
  200. 1. Which file to give the CEO agent first (VISION.md, then CEO_BOOTSTRAP.md)
  201. 2. That they only need to touch VISION.md if their strategic direction changes
  202. 3. That the CEO and CoS generate all other operational documents themselves
  203. ---
  204. ## Quality Checklist Before Output
  205. Before writing the files, verify:
  206. - [ ] Every section of VISION.md has real content — no generic placeholders
  207. - [ ] Pricing model reflects the founder's actual answer (or their live source)
  208. - [ ] Primary target customer is clearly identified, even if secondary ones are listed
  209. - [ ] CEO mandate lists both autonomous AND approval-required items explicitly
  210. - [ ] CEO_BOOTSTRAP Step 4 includes the check-first instruction (update before create)
  211. - [ ] Research → Plan → Execute is in both files in the appropriate form
  212. - [ ] CoS role is defined in VISION.md org structure
  213. - [ ] CEO_BOOTSTRAP checklist covers: agent profiles, OPERATIONS.md, SOPs, phase plan, research tasks
  214. - [ ] Both files feel specific to this company — not like a generic template was filled in
README.md · README · 158 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Paperclip Vision
  2. **A Claude Code skill that interviews your founder and writes the constitution your AI company needs to run itself.**
  3. Paperclip Vision conducts a structured strategic interview and produces two documents that let an AI-run company operate autonomously — without the founder needing to be in the loop for day-to-day decisions.
  4. ---
  5. ## What It Does
  6. Most AI agent setups fail not because the agents are bad, but because they have no clear mandate. They don't know what they're allowed to do, who to escalate to, or what the company is actually trying to accomplish.
  7. Paperclip Vision solves this at the source. It interviews the founder, extracts their strategic intent, and translates it into two machine-readable documents:
  8. | Document | Purpose |
  9. |---|---|
  10. | `VISION.md` | The company constitution. Mission, revenue model, target customer, growth strategy, org structure, CEO mandate, and guiding principles. The CEO agent reads this every heartbeat. |
  11. | `CEO_BOOTSTRAP.md` | One-time activation instructions for the CEO agent. What to do first, in what order, and what to generate so the company can run itself. |
  12. ---
  13. ## How It Works
  14. ### 1. Scans Your Project First
  15. Before asking a single question, the skill reads your working directory — agent profiles, heartbeat files, existing vision documents, phase plans, tech stack, ops files — and uses what it finds to pre-fill context, skip redundant questions, and make the interview feel specific to your company.
  16. ### 2. Structured Founder Interview
  17. A 16-question interview across six sections:
  18. - **The Big Picture** — ultimate goal and 12-month destination
  19. - **Revenue & Customers** — pricing model, revenue target, ideal customer
  20. - **Growth & Marketing** — channels, budget, and sales model
  21. - **Product Direction** — current status and roadmap
  22. - **CEO Autonomy** — what the CEO can do alone vs. what needs your approval
  23. - **Vision & Identity** — companies you admire, success signals, non-negotiables
  24. Questions use single-select, multi-select, and free text. Each answer is acknowledged before moving on. If something is ambiguous or interesting, the skill asks a short follow-up rather than guessing.
  25. ### 3. Generates Both Documents
  26. Once the interview is complete, the skill writes `VISION.md` and `CEO_BOOTSTRAP.md` — fully populated, no placeholders, adapted to your specific company and industry.
  27. ---
  28. ## The Core Philosophy: Research → Plan → Execute
  29. Every VISION.md includes this operating model as a non-negotiable principle. It's what prevents autonomous agents from:
  30. - Publishing too much content too fast and destroying SEO
  31. - Entering communities without understanding the norms and getting banned
  32. - Launching channels without a strategy
  33. **Gate 1 — Research** produces a written output with cited sources.
  34. **Gate 2 — Plan** is reviewed by the Chief of Staff before anything starts.
  35. **Gate 3 — Execute** is scheduled into the master calendar by the CoS.
  36. No execution without a plan. No plan without research.
  37. ---
  38. ## Org Structure
  39. Every company bootstrapped with Paperclip Vision gets the same foundational structure:
  40. ```
  41. Founder
  42. └── CEO Agent
  43. └── Chief of Staff (CoS) Agent
  44. ├── Head of Marketing
  45. │ └── Head of SEO
  46. ├── Head of Sales
  47. └── [department heads per your company]
  48. ```
  49. The **CEO** stays strategic — sets direction, makes decisions, handles escalations.
  50. The **CoS** is the operational backbone — owns the pipeline, the calendar, and inter-agent coordination.
  51. Hiring the CoS is always Step 2 of the bootstrap. It's within the CEO's mandate — no founder approval needed.
  52. ---
  53. ## What Gets Generated
  54. ### `VISION.md` covers:
  55. - Mission statement (what the company does and what it explicitly is not)
  56. - 12-month goal and 3-year vision
  57. - Revenue model and pricing structure
  58. - Primary and secondary target customers
  59. - Growth strategy with channels in priority order
  60. - Sales model
  61. - Product direction and roadmap
  62. - Org chart and role definitions
  63. - CEO mandate — autonomous actions vs. items requiring founder approval
  64. - Reporting cadence
  65. - Guiding principles
  66. - Success metrics at 3-month, 12-month, and 3-year horizons
  67. ### `CEO_BOOTSTRAP.md` covers:
  68. - Step-by-step activation sequence (7 steps, in order)
  69. - Which documents and agent profiles to generate (or update, if they already exist)
  70. - Research sprint tasks before any execution begins
  71. - Channel plans to build from research outputs
  72. - Ongoing operating rhythm (heartbeat → daily → weekly)
  73. - A completion checklist — once all items are checked, governance moves permanently to VISION.md
  74. ---
  75. ## Installation
  76. This skill runs inside [Claude Code](https://claude.ai/code). Install it by adding the `paperclip-vision` skill to your Claude Code skills directory.
  77. ```bash
  78. # Clone into your Claude skills folder
  79. git clone https://github.com/aronprins/paperclip-vision ~/.claude/skills/paperclip-vision
  80. ```
  81. Then invoke it from any project directory:
  82. ```
  83. /paperclip-vision
  84. ```
  85. Claude will scan your current directory and begin the interview.
  86. ---
  87. ## Requirements
  88. - [Claude Code](https://claude.ai/code) (CLI or desktop app)
  89. - A working directory that represents your company (even if mostly empty)
  90. ---
  91. ## Part of the Paperclip Ecosystem
  92. Paperclip Vision is one skill in the broader **Paperclip** framework for building AI-run companies. Other skills in the ecosystem handle agent hiring, task coordination, control plane management, and plugin creation.
  93. > Paperclip is a framework for companies that run on AI agents — not companies that use AI as a tool.
  94. ---
  95. ## Author
  96. Built by [Aron Prins](https://github.com/aronprins).
  97. If you're building an AI-run company on Paperclip and need help with setup, architecture, or consulting — reach out on X:
  98. **[@aronprins](https://x.com/aronprins)**
  99. Follow for updates on Paperclip, new skills, and AI company building.
  100. ---
  101. ## License
  102. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.