Signal
Record customer voices to .docs/feedbacks/ and attach issue analysis.
Input
code
/voice {content}
/voice {content} ({who}, {source})
If metadata is omitted, use "unknown". Date is auto-filled with today.
Steps
- •Use the
.docsskill to read index.md and understand the product vision - •Read
.docs/feedbacks/index.mdto grasp existing themes - •Determine if a similar theme exists
- •Yes: Read that slug.md, append to
## Voices, update## Issuesif needed - •No: Create a new slug.md
- •Yes: Read that slug.md, append to
- •Cross-check against index.md vision, principles, and out-of-scope
- •If the request is outside vision, note it in
## Issues
- •If the request is outside vision, note it in
- •Report analysis briefly
Do not touch index.md. Regenerating index.md is handled by the separate signals-index skill.
slug.md format
FrontMatter:
yaml
---
notion-page-id: {Notion Page ID}
---
Body:
md
# {Theme name}
## Voices
- {Summary of original} [^1]
- {Summary of original} [^2]
## Issues
- {Analyzed issue 1}
- {Analyzed issue 2}
[^1]: "{Original}" ({who}, {YYYY-MM-DD}, {source})
[^2]: "{Original}" ({who}, {YYYY-MM-DD}, {source})
Footnotes hold the original text, who, date, and source. Body stays concise with summaries only.
index.md
index.md is regenerated by the signals-index skill as a categorized narrative with footnotes. Do not edit index.md in this skill.
Output example
code
Appended to account-deletion.md (3rd voice). -> Issue: Missing account deletion flow. Data deletion policy also requested. In scope.