agentleFS
ChianWChianW/C31/skills/product/c31-process/SKILL.md

c31-process

Skill1 starsChanged 3 months agoMITView on GitHub

Output language: Respond automatically in the user's conversation language. Channel 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. 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…

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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
  1. Distinctive:

    Processize before you productize: Every great product started as someone doing the work by hand.

    line 22
  2. Distinctive:

    Ask the user to describe what they want to build.

    line 34
  3. Distinctive:

    If you had to deliver this value with zero technology — just you, a phone, and a spreadsheet — how would you do it?

    line 38
  4. Very specific:

    If you can't name 10 people, you don't know your community well enough yet.

    line 50
  5. Distinctive:

    Document your manual process so clearly that someone else could do it:

    line 67
  6. Distinctive:

    Every interaction teaches you something no amount of building would

    line 87
  7. Distinctive:

    Only automate what you've proven works manually.

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multilingual Triggers

LanguageTrigger phrases
ENc31-process
ZH流程化, 手动先做
JAプロセス化, 手動から始める

Output language: Respond automatically in the user's conversation language.

Minimalist Entrepreneur — Processizer

Channel 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.

Real-World Example: chian.io

Chian's strength is "super-producing, optimizing in use, survival of the fittest." Processizing is the perfect fit: he can manually deliver 10 versions of a knowledge service to his community, measure which resonates, then automate the winner. This skill should emphasize rapid iteration over perfect process design.

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 c31-minimalist-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:

  1. Trigger — What kicks off the process? (Customer emails you, fills out a form, sends a message)
  2. Steps — Numbered list of exactly what to do, in order
  3. Tools needed — What you use at each step (spreadsheet, email, phone, etc.)
  4. Time per customer — How long each step takes
  5. 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.

Cross-References

  • For selecting the community first, use c31-minimalist-community.
  • For validating the idea before processizing, use c31-minimalist-validate.
  • For setting pricing, use c31-minimalist-pricing.

Output

Help the user create:

  1. A one-sentence description of what their product does manually
  2. The magic piece of paper — their full manual process, step by step
  3. A list of 3 specific people to deliver it to this week
  4. Their initial price point
  5. The first step they'll automate when they're ready (not now)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.