Requirement to Code Pipeline Agent Skill
Orchestrates end-to-end frontend development workflows from requirement documents to deliverable React and TypeScript code with mandatory…
- Context cost
- 24.8k tokensestimated from the bundle, loaded when it triggers
- Bundle
- 35 files · 220.6 kB4 scripts among them — read before you run
- Licence
- not declarednone named by its author
- Last change
- —no release on file
- Servers it uses
- Noneruns standalone
What it does
以轻量主控 Pipeline 将需求从需求文档推进到可交付代码；专注于 React + TypeScript Web 前端项目，优先读取项目 AGENTS.md 和 @hupu 组件图谱，保留阶段裁决、组件真源确认、实施前 Gate、review 修复闭环和交付追溯，默认采用聚合执行、core_state 状态和按风险升级的 subagent / 验证策略。
Installed, it changes the agent in these ways.
What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.
And these are the jobs people reach for it for.
The skill itself
A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
24.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
The procedure it runs
The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.
This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
What is in the bundle
35 files, 220.6 kB on disk. Mostly text — the instructions the model reads — with 4 scripts in it that your client would run only if the instructions tell it to.
- SKILL.md17.0 kB
- README.md2.2 kB
- agents/openai.yaml0.4 kB
- evals/prompt-cases.md2.0 kB
- references/artifact-state-contract.md10.7 kB
- references/context-contract.md2.7 kB
- references/manifest-schema.md11.2 kB
- references/platform-routing-contract.md2.0 kB
- references/runtime-contract.md16.3 kB
- references/subagent-contract.md12.0 kB
- scripts/init_requirement_pipeline.py42.9 kB
- scripts/materialize_pipeline_artifact.py6.2 kB
- scripts/pipeline_artifacts.py7.4 kB
- scripts/update_pipeline_state.py65.1 kB
- assets/templates/01-需求分析.md.tmpl1.8 kB
- assets/templates/02-任务拆分.md.tmpl0.5 kB
- assets/templates/02-实施真源确认.md.tmpl1.0 kB
- assets/templates/02-组件影响评估.md.tmpl1.6 kB
- assets/templates/03-代码修改方案.md.tmpl1.9 kB
- assets/templates/03-技术方案.md.tmpl1.1 kB
- assets/templates/04-实施前确认记录.md.tmpl0.6 kB
- assets/templates/04-工程边界清单.md.tmpl1.3 kB
- assets/templates/04-方案复审记录.md.tmpl1.0 kB
- assets/templates/05-本地开发准备记录.md.tmpl0.6 kB
- assets/templates/05-设计资源.md.tmpl1.0 kB
- assets/templates/06-代码生成记录.md.tmpl0.7 kB
- assets/templates/06-实施偏差检查.md.tmpl0.4 kB
- assets/templates/07-代码Review与影响面分析.md.tmpl0.4 kB
- assets/templates/07-测试用例.md.tmpl3.7 kB
- assets/templates/07-验证状态记录.md.tmpl0.4 kB
- assets/templates/08-review问题处理记录.md.tmpl0.3 kB
- assets/templates/analysis-and-plan.md.tmpl1.2 kB
- assets/templates/delivery-summary.md.tmpl0.7 kB
- assets/templates/implementation-and-verification.md.tmpl1.7 kB
- assets/templates/pre-impl-gate.md.tmpl0.6 kB
A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 4 scripts beside the text, so the bundle is 35 files you can review in full before installing.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
# Requirement to Code Pipeline · 24.8k tokens when loaded · macOS, Linux
mkdir -p .claude/skills && t=$(mktemp -d) &&
curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/requirement-to-code-pipeline/bundle.tar.gz &&
tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/requirement-to-code-pipeline" ] &&
{ [ ! -e .claude/skills/requirement-to-code-pipeline ] || { mv .claude/skills/requirement-to-code-pipeline "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } &&
mv "$t/requirement-to-code-pipeline" .claude/skills/ && echo "Installed .claude/skills/requirement-to-code-pipeline"npx mcprush@latest skill add letern1ty/requirement-to-code-pipelineWindows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/requirement-to-code-pipeline/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/requirement-to-code-pipeline/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/requirement-to-code-pipeline" ] && { [ ! -e ~/.claude/skills/requirement-to-code-pipeline ] || { mv ~/.claude/skills/requirement-to-code-pipeline "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/requirement-to-code-pipeline" ~/.claude/skills/ && echo "Installed ~/.claude/skills/requirement-to-code-pipeline" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/requirement-to-code-pipeline/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.
Which clients pick it up on their own
A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.
Versions
Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.
Reviews
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.
Sign inAnybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.