feedback-intake

Routes incoming feedback items to their designated homes in a project workflow.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill feedback-intake-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-intake
Source: https://github.com/happysasha18/live-spec/tree/main/skills/feedback-intake
Command: npx skills add https://github.com/happysasha18/live-spec --skill feedback-intake-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When people hand feedback back to a project — remarks, answers to open questions, screenshots, log files — items get lost, sit unprocessed, or land in the wrong place. This Skill ensures every handed-in item is classified and routed to exactly one home in the same session it arrives, with the person told where it went. ## Core Features & Use Cases - Three-channel intake: Accepts feedback spoken or typed in conversation, answers saved on decision or review pages, and dropped files arriving through the project's inbox folder. - Routing table: Classifies each item as a wish (queued for new behaviour), a same-session fix, an answer closing an open question, field evidence logged to FEEDBACK.md, or a workshop problem logged to .live-spec/PROBLEMS.md. - Append-only feedback ledger: Maintains FEEDBACK.md with one dated line per item recording when it arrived, who handed it in, what it concerns, and where it went. - Use Case: A user reacts to a new export button with "love it, but the file lands in Downloads." The reaction becomes a dated field-evidence line in FEEDBACK.md, while the location request is recognized as a wish and walked to the queue — both halves filed, neither lost. ## Quick Start Ask the agent to sweep the inbox and log any handed-in feedback so each item is routed to its proper home.

Frequently Asked Questions about feedback-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route user feedback in a Claude Code project?▼

Hand the item to the session or drop it in the inbox folder. The skill classifies it via a routing table — wish, fix, answer, field evidence, or workshop problem — and files it in the matching home the same session, then tells you where it went.

How do I log feedback to a project ledger file?▼

Field evidence and plain reactions are appended as dated lines to FEEDBACK.md at the project root. Each line records arrival time, source and channel, the feature concerned, the item in plain words, and its destination.

What happens to files dropped in the inbox folder?▼

Each inbox sweep reads complete deposits and routes them like any other feedback item, committing the route and removing the swept file in one commit. Files with a .draft suffix are skipped until their writer finishes.

When should feedback-intake not be used?▼

Do not use it on the agent's own output, on questions the agent asked, or on remarks merely mentioned without being handed in. It also never opens queue rows on its own judgment and performs no scoring or aggregation of collected feedback.

Does feedback-intake analyze or score collected feedback?▼

No. The skill only receives and routes items to their homes. Reading, scoring, and aggregation of the feedback ledger are deliberately left to the pack's measurement skills.