[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 / Project coordinator workers
All plugins installed	none (no extra plugins beyond the Cursor cloud-agent environment)
Human partner who reviewed this diff	悟空非空也g — reviewed the intended agent behavior (issue tracking for 需求/Bug/咨询, grilling consensus on issues not spec files, consults as issues) in session and explicitly asked to 合入 main

What problem are you trying to solve?

Agents working on wukongnotnull/wukong-code had no project-level rule for recording 需求、Bug、咨询/一般讨论, or grilling consensus, on GitHub issues. Default grilling-skill handoff would write a spec under docs/wukong-code/specs/ as the system of record. The maintainer (悟空非空也g) asked to add collaboration rules to AGENTS.md / CLAUDE.md so agents: create/update issues without re-asking, search first, do not invent fields, record grilling consensus on the issue (not a spec file), and also track consults/discussions as issues even though the web blank-issue form is disabled.

This came from a live session on this repo, not from a theoretical review. Tracking: #49

What does this PR change?

Adds a Chinese collaboration section to CLAUDE.md (canonical; AGENTS.md remains a symlink). Existing English contributor guidelines (PR rejection bar, template, identity disclosure) are unchanged. No skill files, no docs/prd.md, no GitHub repo setting changes.

Is this change appropriate for the core library?

This is contributor-facing process for this repository, not a new runtime skill or a rewrite of skills/grilling. It belongs in the existing AGENTS.md / CLAUDE.md pair that agents already load. A standalone plugin cannot replace repo instruction files. No third-party dependency. Provenance: maintainer-directed session. Maintenance: same as the existing contributor guidelines.

What alternatives did you consider?

• Change skills/grilling/SKILL.md globally so grilling never writes specs. Rejected: skill changes need eval evidence; this PR is one repo-instruction update.
• Write grilling consensus to docs/wukong-code/specs/. Explicitly rejected by the maintainer.
• Redirect consults to README About because blank_issues_enabled: false. Tried, then overridden: maintainer wants consults on issues via API/CLI; do not change repo issue-template settings.
• Copy the rules only into a Cursor store docs/ file. Prefer the repo files.

Does this PR contain multiple unrelated changes?

No. Only CLAUDE.md (plus the existing AGENTS.md symlink). Diff is the collaboration section. docs/prd.md is not included.

Existing PRs

• I have reviewed all open AND closed PRs for duplicates or prior art
• Related PRs: none found for this collaboration-rules change. Open PRs: none. Closest prior art: feat: persist confirmed grilling records as specs before writing-plans #32 (feat: persist confirmed grilling records as specs before writing-plans) — that landed the grilling skill spec-handoff. This PR does not revert feat: persist confirmed grilling records as specs before writing-plans #32; it tells agents that for this repository user instructions in AGENTS.md/CLAUDE.md make the GitHub issue the system of record instead of writing a new spec. Closed docs: route pull requests directly to main #23 / merged docs: target pull requests to main #27 are about targeting PRs at main, not issue tracking.

Environment tested

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

Verified against live GitHub: repo wukongnotnull/wukong-code, issue templates, blank_issues_enabled: false, labels (bug, enhancement, question; platform-support 404), no visible Projects V2. Issue #49 created via API. Did not run a second harness; this is instruction-file text, not executable plugin code.

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

Not applicable. This PR does not add a harness.

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

N/A — not a harness-support PR.

Evaluation

• What was the initial prompt you (or your human partner) used to start the session that led to this change? Maintainer asked to 新建 AGENTS.md with GitHub issue + Projects collaboration rules, fitted to this repo’s real templates and boards.
• How many eval sessions did you run AFTER making the change? Zero wukong-code-evals sessions. This is not a skill-content change. Iteration was in-session: (1) issue/Projects rules, (2) grilling consensus → issue not spec, (3) consults/discussions → issues.
• How did outcomes change compared to before the change? Before: no project collaboration section; grilling skill would spec-handoff; consults were wrongly sent to README About. After: agents are instructed to file 需求/Bug/咨询 on issues, keep grilling consensus on the issue, and not write a spec as system of record.

Language-pack evidence

• Language and support status: 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: n/a
• 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) — not a skills change
• This change was tested adversarially, not just on the happy path — instruction text iterated with the maintainer (three corrections), not multi-session skill evals
• I did not modify carefully-tuned content (Red Flags table, rationalizations, "human partner" language) without extensive evals showing the change is an improvement

No skill files were edited.

Human review

• A human has reviewed the COMPLETE proposed diff before submission

悟空非空也g directed each revision of the collaboration rules and then explicitly asked to 合入 main for this branch only (cursor/agents-md-collaboration-rules-c4e2, through a76621d).