最近做了一条开发 pipeline，想分享一下背后的想法。

我是被 loop / goal engineering、还有 auto-goal（让 agent 自己写 goal、自己 spawn 子任务）那一串东西启发的。但真正让我想通的，是一件关于我自己的事：我的 taste 是“一看就知道”型的，不是“能描述”型的。很多东西我得看到了才知道“不对，不是这个”，事先根本写不清楚。冷著问我要什么，我挤不出来；可给我一个丑原型，我立刻知道哪里不对。

所以这条 pipeline 是反过来走的：先丢一个丑到不行的原型逼出我的反应 →把每个“不对，我要…”抄成一条可检查的规则 →这些规则变成验收标准，让 agent 一项一项开发 →而且每一项都由另一个没参与建造的 agent 独立验收，它没办法自己宣布自己做完了。

对比一下不这样做：你丢一句“帮我做 X”，agent 埋头一路跑到底，最后给你一个打磨得很漂亮、却不是你要的东西——还偏偏是在最贵的时候（结尾）才发现。这条 pipeline 做的，就是把“发现不对”这一刻，挪到最前面、最便宜的时候，而且全程不准 agent 放水、自欺。

灵感来源都很值得读：Lance Martin 讲长时间跑的 agent 会偷懒、自恋、偏离目标；Addy Osmani 讲怎么把 session 里反覆出现的修正，提炼成可复用的规则。

http://github.com/H1an1/idea-to-shipped…

H1an1/idea-to-shipped

Source: https://github.com/H1an1/idea-to-shipped

idea-to-shipped

A taste-driven build pipeline for Claude Code — a package of six skills that take a half-formed idea all the way to a self-running build, without asking you to write a spec, and without losing the parts of “what you want” that you can only recognize once you see them.

It’s built on one fact about how people actually work: your taste shows up when you react to something concrete, not when you’re asked to describe it in advance. So the pipeline never makes you specify everything up front. It makes you react, and it writes down what your reactions reveal.

Formerly roadmap-to-loop — that skill is now just one stage of the larger pipeline.

The pipeline

 idea
   ↓
 1. idea-to-prototype     → an ugly, fast mock-up to react to. You say "no, not that"; it learns.
   ↓
 2. prototype-to-roadmap  → once the picture's firm, it slices it into a buildable, ordered plan.
   ↓
 3. roadmap-to-loop       → turns the plan into LOOP.md: what "done" means, and who checks it.
   ↓
 4. loop-to-goal          → the agent writes its own goals and builds, unattended, checking itself
                            against your criteria, stopping only when it needs your eye.
   ↓
 shipped

 taste-to-rubric          → runs underneath all of it. Every time you react to something — the first
                            mock-up, a mid-build check, final sign-off — it captures the preference
                            into RUBRIC.md so nobody has to ask you twice.

 idea-to-shipped          → the front door: it routes you to the right stage by what you already
                            have, and protects the principles the pipeline is built on.

RUBRIC.md — your taste, written down

Each project grows one file, RUBRIC.md. Every “no, not that” that turns out to be a standing preference (not a one-off tweak) gets distilled into one checkable line, tagged revealed (you only knew it on sight) or known. Over a project it becomes the rulebook the agent checks itself against; rules graduate from “only the owner can judge” to “a verifier subagent can judge” over time. Over many projects, those rulebooks can be compared to distill the constants of your taste — but that’s later, once a few exist.

How to use it

You don’t pick a stage. Just say what you want — “I want something that…” — and the front door (idea-to-shipped) figures out where you are and starts you at the right place. A vague idea starts at the mock-up; if you already have a firm concept or a plan, it jumps in further down.

Your job, start to end, is small and only yours: react (at the first mock-up) and judge (at the gates the agent stops you for). Everything in between is the machine’s.

Install

These are Claude Code skills. Copy the ones you want into your personal skills directory:

git clone https://github.com/H1an1/idea-to-shipped.git
cp -R idea-to-shipped/skills/* ~/.claude/skills/

Each skill is a self-contained skills/<name>/SKILL.md; its description controls when Claude reaches for it. You can also drop them into a project’s .claude/skills/ instead, to scope them to one repo.

The skills

What’s intentionally not built yet

• The cross-project master rubric (needs several projects’ RUBRIC.md to compare).
• Auto-loading rules back in / scoring — its shape will reveal itself once real rules pile up.

These come with mileage, not design. Run the pipeline on real things first; the next pieces will show you their shape.