docs-feedback-triage
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- docs-feedback-triage
- license
- MIT
- metadata
- { "tags": "developer-docs,technical-writing,documentation,feedback,triage", "version": "0.1.0", "category": "Writing", "displayName": "Docs Feedback Triage" }
- description
- Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 3
- 参考文档guidelines.md1.6 KB
- 参考文档references/core/knowledge.md8.1 KB
- 参考文档workflows/triage-doc-feedback.md2.5 KB
03 SKILL.md 正文
Docs Feedback Triage
Use this skill to turn developer documentation feedback into valid, actionable, prioritized work. It helps agents avoid treating every comment as equal while preserving user evidence.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 8, "Gathering and integrating feedback." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 5, "Customer Feedback and Community," Chapter 18, "Working with Customer Support," and Chapter 20, "Working with the Field." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.mdto choose the smallest useful reference set. - Identify feedback source, affected doc, user impact, response need, and whether the issue is docs-owned.
- Test validity, actionability, and importance before recommending work.
- Use
workflows/triage-doc-feedback.mdfor a full triage pass. - Close the loop with users or source teams when the feedback changes product, support, or docs work.
Default Output
When triaging feedback, return:
- Feedback summary - source, affected doc, user type, and reported problem.
- Classification - valid/invalid/needs research, docs/product/support issue, duplicate status.
- Actionability - reproducible, scoped, and fixable information.
- Priority - severity and rationale.
- Recommended action - doc fix, routing, follow-up, or no action.
- Follow-up - user response, owner, and evidence to collect.
Contents
| Need | Start Here |
|---|---|
| Understand feedback channels | references/core/knowledge.md |
| Apply triage rules | references/core/knowledge.md |
| See triage examples | references/core/knowledge.md |
| Triage feedback | workflows/triage-doc-feedback.md |
| Route by task | guidelines.md |
Core Posture
- Feedback is evidence, not a direct order.
- Distinguish docs problems from product, support, pricing, or policy problems.
- Prioritize by user impact and fixability.
- Treat public/community feedback as both support signal and trust-building opportunity.
- Follow up when users took time to report a real issue.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.