Generated from
cat-harness/skills/authoring/content-lifecycle/content-feedback.md— do not edit here. Typed contract: schema reference.
Content Feedback Collection
Gather and triage feedback on published content for future iterations.
Responsibilities
- Collect feedback from implementers and users
- Triage feedback by severity and scope
- Map feedback to specific content components
- Create issues/tickets for actionable feedback
- Prioritize feedback for next iteration
- Coordinate with clinical SMEs for clinical feedback
- Track feedback resolution across versions
Actors
- Technical Officer (triage lead)
- Programme Manager (prioritization)
- Clinical SME (clinical feedback assessment)
- Business Analyst (implementer feedback)
Inputs
- Published content (current version)
- User/implementer feedback (issues, comments, surveys)
- Country implementation reports
Outputs
- Triaged feedback log
- Prioritized backlog for next iteration
- Change requests linked to feedback
Staging links
When a staging preview exists, every request this skill makes for feedback,
review or sign-off carries it: one deep link per changed page, to the anchor
where the change sits, with the same page on main as before. Where the skill
declares an output contract, they go in its stagingLinks field. The rule, and
where the page list comes from:
staging-review §”The deep-link rule”.
Processes that run this skill
| process | step(s) that name it |
|---|---|
| Narrative review | Record findings as advice |
| Adjudication | State the finding and what it read |
| Prose and the code it describes | Raise a finding against the wrong side |
| Questionnaire wireframe review | Triage the change request |
| Content lifecycle | Triage published feedback; File feedback as beans |
| Draft, review and publish | Open beans for the change requests |