Individual skill
plan-comments-and-feedback
Plan review threads end to end: what `get-plan-feedback` returns, how to read anchors, resolver intent, replies, notification email, deletion, and abuse reports. Use when reading, answering, resolving, or removing plan feedback.
templates/plan/.agents/skills/plan-comments-and-feedback/SKILL.md
Source commit 3ec46d2df6a396c23a8e910c0ac3c2f13f574958
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 7,647
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents Repository topic
- ai Repository topic
- react Repository topic
- agent-native Repository topic
- typescript Repository topic
- agent-framework Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- framework Repository topic
- generative-ui Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Plan Comments and Feedback
- Plan comments include reviewer identity, @mentions, resolver intent
(`agent` or `human`), exact anchors, and design-review threads. When adding
human feedback through `update-visual-plan`, preserve `authorEmail` and
`authorName` when known; pass `parentCommentId` to reply inline to an
existing comment thread. Text feedback should anchor to the nearest prose
block, and visual/canvas feedback should include target coordinates plus
concise surrounding context.
- Use `delete-plan-comment` only when the user explicitly asks to remove a
comment, undo an accidental comment, or clean up an obsolete thread. Deleting
is a soft delete: normal comment views hide the comment while the database row
remains for audit/debugging. Deleting a thread root also deletes its replies.
When feedback has merely been handled, prefer `resolve-plan-comment` and