[wukongnotnull]

This PR MUST target the main branch. Active work is developed on
focused branches and merged directly into main after review.

Who is submitting this PR? (required)

Field	Value
Your model + version	Cursor Grok 4.6
Harness + version	Cursor cloud agent
All plugins installed	This session ran as a Cursor cloud agent on the wukongnotnull/wukong-code checkout. Native Cursor tools plus MCP namespaces Gmail, Outlook, cursor-cloud, and cursor-subscriptions were available. No additional marketplace plugins were declared in the session. The change is documentation only and does not depend on those MCP servers.
Human partner who reviewed this diff	悟空非空也g — requested a grounded prd.md, asked for Simplified Chinese, reviewed the 简体正文, then explicitly asked to merge this workstream into main

What problem are you trying to solve?

悟空非空也g asked to 对该项目补充一份 prd.md. The repository had README (install/overview), AGENTS.md / CLAUDE.md (contributor rules), dated specs/plans, and operator docs (docs/testing.md, docs/evals-setup.md, docs/porting-to-a-new-harness.md), but no living product-requirements document that states purpose, audience, in/out of scope, capabilities, and how success is judged.

That gap showed up in this session: agents and humans had to reconstruct product constraints from many files. After the English snapshot was written, the same human asked 改成中文, then 查阅一下简体中文, then 合入 main for this branch only.

What does this PR change?

Adds docs/prd.md: a Mainland Simplified Chinese product-requirements snapshot of what this repo already ships (skills, harness bootstrap, core vs standalone plugins, evals, PR bar). One file. No skill, hook, or AGENTS.md/CLAUDE.md changes.

Is this change appropriate for the core library?

Yes, as documentation of the existing core plugin, not as a new skill.

• Who has the problem: operators, contributors, and agents working on Wukong Code itself who need a single product snapshot next to the other durable docs under docs/.
• Why core instead of a standalone plugin: it describes this repository. A separate plugin cannot be the project's PRD.
• Externally sourced: no. The PRD cites Superpowers, OpenAI Product Design, and Anthropic frontend-design only as provenance already recorded in THIRD_PARTY_NOTICES.md / product-design.lock.json.
• Runtime or tool dependencies: none. Markdown only.
• Evidence: grounded in README, contributor docs, skills inventory, harness list, and eval/PR gates already in tree. No unshipped features. Human 悟空非空也g reviewed the 简体正文.

What alternatives did you consider?

1. Root prd.md — rejected. Durable operator docs already live in docs/; README stays the install/overview.
2. Dated file under docs/wukong-code/specs/ — rejected. That tree is historical feature specs, not a living product snapshot.
3. Extending README instead of a PRD — rejected. README is already the install surface; a requirements snapshot would make it longer without helping the contributor/agent audience.
4. Linking from README — rejected. README does not catalog docs/, so a missing link would not be inconsistent.
5. Bundling the AGENTS.md/CLAUDE.md collaboration-rules branch — rejected. One problem per PR; that work is a separate branch.

Does this PR contain multiple unrelated changes?

No. Diff is only docs/prd.md.

Existing PRs

• I have reviewed all open AND closed PRs for duplicates or prior art
• Related PRs: none found

Searched open and closed PRs for prd, prd.md, 产品需求, and PRD. No existing PR adds a product-requirements document. Nearby docs PRs (#46 release notes, #42 evals raw JSONL, #27/#23 PR targeting main) are unrelated.

Environment tested

Harness (e.g. Claude Code, Cursor)	Harness version	Model	Model version/ID
Cursor cloud agent	Cursor cloud agent (this run)	Cursor Grok 4.6	Cursor Grok 4.6

Checks performed on the document itself: Traditional vs Simplified character scan (none); TW/HK wording vs Mainland 简体 (none: no 軟體/檔案/資訊/品質/專案); Chinglish and leftover English body (fixed on this branch); remaining English is product/harness/skill names and paths by request.

This is not a skill or harness-runtime change, so no agent session was run against a consumer project.

New harness support (required if this PR adds a new harness)

Not applicable. This PR does not add a harness, bootstrap, or install path.

Clean-session transcript for "Let's make a react todo list"

N/A — this PR does not add harness support. Acceptance test does not apply.

Evaluation

• What was the initial prompt you (or your human partner) used to start the session that led to this change? 对该项目补充一份 prd.md (grounded in the repo only). Follow-ups: 改成中文; 查阅一下简体中文; then 合入 main for cursor/docs-prd-b0bf only.
• How many eval sessions did you run AFTER making the change? Zero skill-behavior eval sessions (wukong-code-evals / Drill). This is a documentation file; skill bodies were not modified.
• How did outcomes change compared to before the change? Before: no living PRD. After: docs/prd.md exists in Simplified Chinese, scoped to shipped behavior. Language review found and fixed concrete issues (e.g. cohort mistranslated as 队列; compaction left in English; 领域向 / 树中当前版本 / 运维文档 calques). No before/after agent-compliance delta because no skill text changed.

Language-pack evidence

• Language and support status: N/A — not a language pack
• Real failure generic methodology handled incorrectly: N/A
• Project markers and toolchain versions: N/A
• Official sources: N/A
• No-guidance repetitions and failures: N/A
• With-guidance repetitions and results: N/A
• Monorepo, unsupported-language, and docs-only controls: N/A
• Human reviewer familiar with the language: 悟空非空也g reviewed the 简体正文
• Frameworks or third-party preferences introduced: none

Rigor

• If this is a skills change: I used wukong-code:writing-skills and completed adversarial pressure testing (paste results below)
• This change was tested adversarially, not just on the happy path
• I did not modify carefully-tuned content (Red Flags table, rationalizations, "human partner" language) without extensive evals showing the change is an improvement

Not a skills change, so writing-skills was not applicable. Adversarial pass on the PRD was the Mainland 简体 review (character set, TW/HK lexicon, Chinglish, leftover English). Skill Red Flags / rationalizations / "human partner" language in skill files were not edited. The PRD cites “human partner” as existing contributor terminology.

Human review

• A human has reviewed the COMPLETE proposed diff before submission

悟空非空也g reviewed the Simplified Chinese PRD, then explicitly asked to merge this branch (cursor/docs-prd-b0bf) into main. AGENTS.md/CLAUDE.md work is excluded from this PR.