processize
Skill9 starsChanged 7 months agoMITView on GitHub
Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.
7 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- scaccogatto/minimalist-entrepreneuredited, first seen Oct 15, 2026
- lglucas/ai-dev-operating-systemtheir own version, first seen Sep 28, 2026
- suvimatt/agent-bootstrappertheir own version, first seen Aug 31, 2026
- kalias/OPC_starter_skillstheir own version, first seen Jul 20, 2026
- keeea/minimalist-entrepreneur-skillsedited, first seen Apr 16, 2026
- consubstantial-polistes407/skillsword for word, first seen Mar 23, 2026
Other versions7 projects use a version of this.
Word for word · 2
- slavingia/skills★ 11k100% same
- consubstantial-polistes407/skills★ 0100% same
Edited · 2
- keeea/minimalist-entrepreneur-skills★ 1961% same
- scaccogatto/minimalist-entrepreneur★ 192% same
Wrote their own version · 3
- lglucas/ai-dev-operating-system★ 12same name
- kalias/OPC_starter_skills★ 1same name
- suvimatt/agent-bootstrapper★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository140 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alex-hormozi-pitchSkill
- AlgorithmSkill
- AnnualReportsSkill
- ArtGeneratorSkill
- artSkill
- autoplanSkill
- autoresearchSkill
- benchmarkSkill
- brainstormingSkill
- brand-guidelinesSkill
- brightdataSkill
- browseSkill
- BugHunterSkill
- CallIntelligenceSkill
- canarySkill
- canvasSkill
- carefulSkill
- ceo-advisorSkill
- cfo-advisorSkill
- cmmcSkill
- codebase-indexerSkill
- codexSkill
- CodingAgentSkill
- company-valuesSkill
- connect-chromeSkill
- CORESkill
- system-createcliSkill
- CreateskillSkill
- csoSkill
- cto-advisorSkill
- CybersecurityPlaybooksSkill
- defuddleSkill
- design-consultationSkill
- design-reviewSkill
- DevTeamSkill
- DiscordAdminSkill
- document-releaseSkill
- document-writerSkill
- doraSkill
- dpdpaSkill
- EmailManagerSkill
- executing-plansSkill
- fabricSkill
- fedrampSkill
- ffuf-web-fuzzingSkill
- find-communitySkill
- first-customersSkill
- FirstPrinciplesSkill
- form-croSkill
- freezeSkill
- gdpr-complianceSkill
- git-worktreesSkill
- GovernanceSkill
- grow-sustainablySkill
- gstack-upgradeSkill
- guardSkill
- hipaa-complianceSkill
- investigateSkill
- iso27001Skill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Processize before you productize: Every great product started as someone doing the work by hand.
- Distinctive: line 18
Ask the user to describe what they want to build.
- Distinctive: line 22
If you had to deliver this value with zero technology - just you, a phone, and a spreadsheet - how would you do it?
- Very specific: line 34
If you can't name 10 people, you don't know your community well enough yet.
- Distinctive: line 51
Document your manual process so clearly that someone else could do it:
- Distinctive: line 71
Every interaction teaches you something no amount of building would
- Distinctive: line 75
Only automate what you've proven works manually.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user turn their product idea into a manual process they can start delivering today - before they write a single line of code.
Core Principle
Processize before you productize. Every great product started as someone doing the work by hand. Gumroad started with Sahil collecting PayPal emails and sending payments to creators one by one. Your product should start the same way.
"Most apps on the internet are just forms and lists."
Your job right now is not to build software. It's to prove you can deliver value to real people, manually.
Step 1: What's the Product Idea?
Ask the user to describe what they want to build. Then strip it down:
- What is the one thing this product does for a customer?
- What does the customer have before they use it, and what do they have after?
- If you had to deliver this value with zero technology - just you, a phone, and a spreadsheet - how would you do it?
"Can I ship it in a weekend?" If not, reduce scope until you can.
Step 2: Who Needs This Today?
Connect the idea back to a real community:
- Who is already trying to solve this problem with a workaround?
- Where do these people hang out? (Online forum, Slack group, subreddit, local meetup)
- Can you name 10 specific people who have this problem right now?
If you can't name 10 people, you don't know your community well enough yet. Go back to /find-community.
Step 3: Design the Manual Version
This is the heart of processizing. Walk through exactly how you'd deliver the product's value by hand:
- What does the customer give you? (An email, a file, a description of what they need)
- What do you do with it? (Every step, in order)
- What do you give back? (The deliverable)
- How long does it take you? (Per customer)
Before Gumroad was software, Sahil collected PayPal emails and paid creators one by one. The "product" was Sahil doing it manually.
Be specific. "I process their request" is not a step. "I open their email, copy the file link, run it through X, format the output, and email it back within 2 hours" is a step.
Step 4: Write the Magic Piece of Paper
Document your manual process so clearly that someone else could do it:
Write down every step you take on a piece of paper. This is your "magic piece of paper" - if you went on vacation, someone else could pick it up and keep the business running.
Your magic piece of paper should include:
- Trigger - What kicks off the process? (Customer emails you, fills out a form, sends a message)
- Steps - Numbered list of exactly what to do, in order
- Tools needed - What you use at each step (spreadsheet, email, phone, etc.)
- Time per customer - How long each step takes
- Handoff - How you deliver the result back to the customer
Step 5: Charge for It
"There is a massive difference between free and $1."
The zero price effect means free users give you zero signal. Charging even $1 proves someone values what you do.
- Set a price based on the time it takes you and the value to the customer
- Reach out to 3 people from your community this week
- Deliver the manual version and collect payment
- Every interaction teaches you something no amount of building would
Step 6: When to Productize
Only automate what you've proven works manually. Signs you're ready:
- You've delivered the manual version to 10+ paying customers
- You can predict exactly what they'll ask for
- The steps on your magic piece of paper haven't changed in weeks
- You're spending more time on delivery than on finding customers
Then - and only then - automate one step at a time. The first thing to automate is whatever takes you the most time per customer.
Output
Help the user create:
- A one-sentence description of what their product does manually
- The magic piece of paper - their full manual process, step by step
- A list of 3 specific people to deliver it to this week
- Their initial price point
- The first step they'll automate when they're ready (not now)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

