# easychen/opc-methodology: A Markdown Book on One-Person Businesses, Plus an Agent Skill Set

> The second edition of 《一人企业方法论》 is an mdBook project with a Chinese-language book, an infrastructure chapter, and a 2026-04 agent skill set. Here is what is actually in the repository, how to build the EPUB yourself, and where the CC-BY-NC-SA licence bites.

**easychen/opc-methodology** — 《一人企业方法论》第二版，也适合做其他副业（比如自媒体、电商、数字商品）的非技术人群。

- Repository: https://github.com/easychen/opc-methodology
- Website: https://ft07.com/opb-quick-start?mtm_campaign=github&mtm_kwd=opbmv2
- Stars: 16,822 · Forks: 1,906
- Language: PHP
- License: NOASSERTION
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/easychen-opc-methodology

## What easychen/opc-methodology actually is, and who it is written for

The repository is the source of the second edition of 《一人企业方法论》, a book of roughly 60,000 Chinese characters about running a one-person business. The README frames the shift from the first edition as a move away from independent software development toward a general methodology: non-technical readers can produce digital goods, or build an online service on top of NoCode tools or open source projects with AI assistance. That audience statement matters, because the repository is not a library you import. It is a manuscript plus a small set of supporting artifacts, and the primary language field says PHP only because of tooling around the text, not because the project ships a PHP package.

The book is organised in four parts: defining a one-person business, planning it, building it, and infrastructure. The fourth part is new in the 2.1 revision, covering user pools and reach, content pools and automation, product pools and payment, and crowdsourcing. The README describes that chapter as filling the gap between theory and practice. If you have read business writing that stops at strategy and never names a payment flow, that is the gap being claimed here. Whether the chapter closes it is something you judge from the text, not from the README.

Two artifacts sit outside the book. The first is an agent skill set added in 2026-04, with its own site and a video walkthrough on Bilibili. The second is 《方糖真实创业模拟器》, a business simulation sandbox the author built with AI so readers can rehearse strategies against the methodology. Both are linked from the README rather than contained in the repository, so treat them as companion services with their own availability.

## Repository layout: a manuscript, a book.toml and a skills directory

The top-level entries are .gitignore, LICENSE, README.md, book.toml, skills/, src/ and words.sh. That list tells you most of the architecture. book.toml is the mdBook configuration, so the book is built by mdBook rather than by a custom static site generator. src/ holds the manuscript and the images referenced in the README, including the cover and the skill-set screenshot. skills/ is the agent skill set. words.sh is a word-counting script, which is consistent with a project whose README talks about the text growing from a long article into a book of a stated length.

The data flow is therefore short and unremarkable, which is a point in its favour for a book repository. You edit Markdown under src/, mdBook renders HTML, and mdbook-epub produces a standalone EPUB. There is no database, no service to run, no API surface. If you were hoping for a tool that generates a business plan for you, this is not that. The methodology is prose. The only executable pieces are the build tooling and whatever the skills/ directory contains.

One consequence of this layout is that the interesting engineering question is not how the code works but how the text is versioned. A book in a Git repository means chapters can be diffed, translated and forked, and the CC-BY-NC-SA terms explicitly contemplate derivative works under the same licence. The cost is that a reader who wants a stable, citable edition has to pick a commit, because the default branch is master and the README describes a 2.1 revision that arrived after the 2.0 release.

## Building the EPUB yourself with mdbook-epub

The README gives exactly one build instruction for the ebook: use the mdbook-epub tool, run it with the standalone flag, and the resulting EPUB appears in the book directory. There are no version pins in the README for mdBook or mdbook-epub, so install both from their usual sources and be prepared to match versions if the render fails.

The command as documented is:

```bash
mdbook-epub --standalone true
```

After it finishes, look in the book directory for the generated .epub file. If you prefer to read in a browser first, plain mdBook serves the HTML version from the same src/ tree, which is the normal way to check that a chapter renders before committing to an EPUB build.

If you only want the finished ebook, the README points to a download page rather than asking you to compile anything:

```bash
# README points to the download page instead of a build step
# https://ft07.com/opb-book-index/
```

For the agent skill set, the README links a dedicated site and a video explanation. It does not document an installation command, a package name or a version for the skill set in the README text, so do not invent one: read the skill-set site and the skills/ directory before wiring anything into an agent. The same caution applies to the simulation sandbox, which is hosted at its own URL and described only as something you can use alongside the methodology.

## The licence is the real constraint, not the tooling

The README states that the book is published under CC-BY-NC-SA. The three parts of that licence each do work here. Attribution means you must credit the author and link back to the GitHub repository. NonCommercial means you may not use the work for commercial purposes. ShareAlike means derivative works must carry the same licence terms.

For a methodology aimed at people building businesses, that is an awkward fit, and it is worth naming plainly rather than glossing over. You can read the book, share it, translate it and remix it. You cannot turn the text into a paid course, bundle it into a commercial product, or sell an English edition. The repository's LICENSE entry is reported as NOASSERTION, which means automated licence detection could not classify it; the README's CC-BY-NC-SA statement is the authoritative description of intent, and you should read the LICENSE file itself before relying on either. This is a description of what the documents say, not legal advice.

The practical effect is that the project is open to readers and closed to commercial reuse of the text. If your plan is to build a product inspired by the methodology, the licence governs the text, not your product. If your plan is to republish the text, the licence governs you directly.

## Where this is the wrong tool

The most obvious limitation is language. The book is written in Chinese, the README is in Chinese, and the linked chapters are Chinese pages. The README does not describe an official English translation. An English-speaking reader can still use the repository, but only by reading machine-translated chapters or waiting for a community translation, and the CC-BY-NC-SA ShareAlike term means any such translation inherits the same restrictions.

A second limitation is that the repository is a book, not a framework. There is no CLI that audits your business, no template engine that emits a plan, no configuration schema beyond book.toml. If you want tooling, the agent skill set and the simulation sandbox are separate destinations, and the README does not specify how the skills integrate with any particular agent runtime. Anyone expecting a drop-in package will be disappointed by a directory of Markdown and a shell script.

A third issue is maintenance signal. The last push to the repository was on 2026-04-23, and the only listed release is 2.0 from 2024-03-27. The README describes a 2.1 revision that is not reflected in the release list, so the release page and the manuscript are out of step. None of this makes the book wrong, but a reader who wants a tagged, frozen edition has to use a commit hash rather than a release.

## How it differs from the usual indie-hacker reading list

The closest comparison is the body of English-language writing on indie hacking and solo software businesses, which tends to be published as blog archives, paid newsletters or self-published ebooks with no source repository. The difference in approach is structural: here the manuscript lives in Git, the build is reproducible through mdBook, and the licence is an explicit Creative Commons variant rather than an all-rights-reserved notice. You can fork the text, diff two revisions, and compile your own EPUB. You cannot do that with a newsletter archive.

The second difference is scope. Indie-hacking material usually assumes you write software. This book explicitly widens out to non-technical readers producing digital goods or assembling services from NoCode tools and open source projects with AI help, and the infrastructure chapter talks about user pools, content pools, product pools and crowdsourcing as capabilities rather than as code. If you already have a software background, parts of that framing will read as restating things you know. If you do not, it is the section most likely to be useful.

The third difference is the companion simulation. Most methodology books stop at the text. Here the author points readers at a business simulator built with AI for strategy rehearsal, which is an unusual pairing and worth evaluating on its own terms rather than taking on trust.

## Maintenance, upgrades and what a fork costs you

The repository is not archived, and the last push was on 2026-04-23. The only release in the list is 2.0, dated 2024-03-27, so the gap between the release and the current manuscript is roughly two years of edits that were never tagged. If you depend on a stable text, pin a commit and record it; if you depend on the release page, you are reading an older revision than the README describes.

Upgrade cost is low in the technical sense. There are no dependencies to bump beyond mdBook and mdbook-epub, no runtime, no migrations. The real cost of a fork is editorial: if you translate or adapt the book, ShareAlike means your version carries the same licence, and NonCommercial means you cannot sell it. Any fork also inherits the maintenance burden of tracking a moving master branch, because the upstream project does not appear to publish tagged revisions for each editorial pass.

On the plus side, a book in Markdown is about as cheap to keep alive as software gets. The failure mode is not a broken build; it is a stale fork that silently diverges from a manuscript the author keeps editing.

## Conclusion

Adopt it if you are a solo operator or side-project builder who reads Chinese and wants a structured methodology plus a buildable EPUB, or if you want to inspect the skills/ directory before wiring the skill set into an agent. Do not adopt it if you need an English text or a permissive licence for a commercial product: the CC-BY-NC-SA terms bar commercial use, and the README does not describe an official translation. Verify three things first: the licence file at the repository root, whether the skills/ directory matches the skill-set site you intend to use, and whether mdbook-epub still builds cleanly against the current book.toml, since the README gives only the one command and no version pins.

## FAQ

### What does OPC stand for in easychen/opc-methodology?

The repository name uses opc as shorthand for the one-person company idea behind 《一人企业方法论》. The README itself does not spell out the acronym, so the expansion comes from the project name rather than from a definition in the text.

### How do I build the EPUB for easychen/opc-methodology myself?

The README says to use the mdbook-epub tool with the standalone flag, and the EPUB is then placed in the book directory. If you would rather not compile it, the README links to a download page for the finished ebook.

### Can I use easychen/opc-methodology in a commercial product?

The README states the book is released under CC-BY-NC-SA, which forbids commercial use and requires attribution plus the same licence for derivative works. The repository's LICENSE entry is reported as NOASSERTION, so read the LICENSE file directly before relying on it.

### Is there an English version of easychen/opc-methodology?

The README does not describe an official English translation; the book, the README and the linked chapters are all in Chinese. Any community translation would fall under the ShareAlike term of CC-BY-NC-SA.

## Sources

- [easychen/opc-methodology on GitHub](https://github.com/easychen/opc-methodology)
- [Issues](https://github.com/easychen/opc-methodology/issues)
- [Project website](https://ft07.com/opb-quick-start?mtm_campaign=github&mtm_kwd=opbmv2)
- [README](https://github.com/easychen/opc-methodology/blob/master/README.md)
- [Releases](https://github.com/easychen/opc-methodology/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/easychen-opc-methodology