Content Feedback

Skill id: content-feedback

Generated from JSON Schema — do not edit by hand. Run bun run cat-harness-tools/scripts/gen-schema-docs.ts.

Input

Input schema for feedback collection and triage.

FieldTypeRequiredDescription
source"github-issues" | "survey" | "implementation-report" | "clinical-review"yesSource of feedback.
publishedVersionstringnoVersion the feedback relates to.
feedbackItemsarrayno
stagingLinksanynoThe staging preview of the work under review, as the request for feedback carried it, so the reviewer opens the changed pages rather than rebuilding links. Rule: cat-harness skills/sdlc/sdlc-core/staging-review.md §”The deep-link rule”.

feedbackItems[]

FieldTypeRequiredDescription
descriptionstringyes
severity"critical" | "major" | "minor" | "enhancement"no
componentstringno
reporterstringno

Raw schema · ✎ Edit

Output

Output schema for triaged feedback.

FieldTypeRequiredDescription
triagedItemsarrayyes
summaryobjectno
stagingLinksanynoThe staging preview of the work this output asks a person to look at: one deep link per changed page, with the same page on main. Required whenever a preview exists; when it does not, say so in missing. Rule: cat-harness skills/sdlc/sdlc-core/staging-review.md §”The deep-link rule”.

triagedItems[]

FieldTypeRequiredDescription
idstringyes
priority"P0" | "P1" | "P2" | "P3"yes
disposition"backlog" | "next-sprint" | "wont-fix" | "duplicate" | "needs-info"yes
assigneestringno
linkedIssuestringno

summary

FieldTypeRequiredDescription
totalintegerno
criticalintegerno
majorintegerno
minorintegerno
enhancementintegerno

Raw schema · ✎ Edit


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed b08c961 · 2026-10-23T23:11:09Z