Repository navigation
Grilling: track consensus on issues; write a separate technical spec #49
Description
- I searched existing issues and this has not been proposed before
What problem does this solve?
In this repository, grilling / 「逐题问清楚」共识 if written to docs/wukong-code/specs/ becomes a new system of record that duplicates GitHub tracking and is easy for agents to treat as unfinished work. The maintainer (悟空非空也) asked that grilling consensus be recorded on a GitHub issue instead, and that agents not drop a spec markdown file as the source of truth.
This came from a real session adding project collaboration rules to AGENTS.md / CLAUDE.md, not from a theoretical review.
Proposed solution
Keep existing contributor guidelines. In AGENTS.md / CLAUDE.md (same file: AGENTS.md → CLAUDE.md):
- After grilling consensus with the human partner, create or update a GitHub issue on
wukongnotnull/wukong-codewith background, decisions, open questions, and follow-ups. Search first; do not duplicate. Issue create/update is already authorized. - Do not write that consensus to disk as a spec (
docs/wukong-code/specs/, new spec markdown, or a design-spec file as system of record). Dated historical specs/plans are reference only. - If
docs/prd.mdalready exists, treat it as a product snapshot; grilling outcomes still go to the issue. - User instructions in this file override the
grillingskill handoff that writes and commits a spec for work in this repository.
Implementation is on branch cursor/agents-md-collaboration-rules-c4e2. No PR until a human reviews the complete diff.
What alternatives did you consider?
- Changing
skills/grilling/SKILL.mdglobally so grilling never writes specs. Rejected for this change: one focused repo-instruction update; skill changes need eval evidence. - Writing a new spec under
docs/wukong-code/specs/to archive the consensus. Explicitly rejected by the maintainer. - Copying the collaboration section only into a Cursor store
docs/file. Prefer the repoAGENTS.md/CLAUDE.md.
Is this appropriate for core Wukong Code?
This is contributor-facing process for this repository (wukongnotnull/wukong-code), not a new runtime skill. It belongs in the existing AGENTS.md / CLAUDE.md pair. A standalone plugin is the wrong vehicle.
Environment (required)
| Field | Value |
|---|---|
| Wukong Code version | checkout of wukongnotnull/wukong-code at the collaboration-rules branch |
| Harness (Claude Code, Cursor, etc.) | Cursor Cloud Agent |
| Harness version | Cursor Cloud Agent (this run) |
| Your model + version | Cursor Grok 4.6 |
| All plugins installed | none beyond the Cursor Cloud Agent environment |
Context
- Repo files:
CLAUDE.md(canonical),AGENTS.mdsymlink. - Branch:
cursor/agents-md-collaboration-rules-c4e2 - Related commits:
f245d8d(issue/Projects collaboration section),335d9ac(grilling consensus → issue, not spec) - Searched issues: only unrelated closed Want to add your plugin to awesome-ai-plugins? #25 (
awesome-ai-plugins); no open/closed match for AGENTS.md collaboration or grilling-to-issue. - No GitHub Project board was visible with current permissions; not claimed as auto-added.
Activity
wukongnotnull commentedon Oct 13, 2026
Update (2026-10-13): grilling HANDOFF clarification
Maintainer (悟空非空也g) clarified in a real session: the previous AGENTS.md wording (“never write a spec; issue is the system of record”) is wrong. Issue/board tracking stays a repo development habit, not a grilling skill capability. Do not change
skills/grilling/SKILL.mdfor this.Handoff: 确认记录 → 根据确认后的记录写 spec 技术规格文档（不要把确认记录自己当成 spec 文档）→ 审核 spec 文档 → 再
writing-plans.Decided:
docs/prd.mdas a grilling spec substitute.Searched open and closed issues/PRs: this issue (#49) is the matching tracker (title previously said “not spec files”). Related merged PRs: #50 (collaboration rules / old grilling-to-issue text), #32 (skill-level persist-record-as-spec). No new issue opened.
Implementation is on branch
cursor/grilling-spec-handoff-9b62(1b3542e). No PR until a human reviews the complete diff.Identity
[-]Record grilling consensus on GitHub issues, not spec files[/-][+]Grilling: track consensus on issues; write a separate technical spec[/+]wukongnotnull commentedon Oct 13, 2026
Update (2026-10-13): HANDOFF belongs in the grilling skill
Maintainer (悟空非空也g) decided the grilling HANDOFF sequence is for plugin users and therefore belongs in
skills/grilling/SKILL.md, not this repo’sAGENTS.md. Issue/board tracking stays a 本仓库开发习惯 inAGENTS.md/CLAUDE.mdonly. Do not put GitHub issue/Projects into the skill.HANDOFF (skill): 确认记录 → 根据确认后的记录写 spec 技术规格文档（不要把确认记录自己当成 spec 文档）→ 审核 spec 文档 → 再
writing-plans.docs/wukong-code/specs/YYYY-MM-DD-HHmm-<topic>-design.mdunless the human prefers another path).writing-plansonly after they approve that file.AGENTS.mdgrilling section was slimmed to issue/board tracking and a pointer at the skill. It no longer duplicates or overrides HANDOFF.Branch / identity
cursor/grilling-spec-handoff-9b62(840317c; earlier AGENTS-only1b3542esuperseded in intent)Existing PRs
Searched open and closed: #32 (merged persist-record-as-spec), #50 (merged collaboration rules / old “issue not spec”), #13 (grilling skill). No open duplicate.
Evaluation (honest)
evals//wukong-code-evalshas no grilling scenarios (language-guidance branch is JS/TS jsonl only). No Drill/API-key tmux run. Isolated Cursor subagent RED/GREEN is indocs/wukong-code/evals/2026-10-13-grilling-derived-spec-handoff.md: RED dumped the eight-section record as the spec; GREEN wrote a derived six-section technical spec, waited for file review, then loadedwriting-plansonly after按这个写计划. Early-stop wrote no file. Not a Drill cohort; not fabricated.wukongnotnull commentedon Oct 13, 2026
Merged #55 into
mainafter 悟空非空也g said 合入. CI: lint pass, test pass. Board Status set to Done.