log-feedbacklisted

# Skill: log-feedback The complete, canonical contract for this skill is the paste-prompt it wraps, inlined here — **follow it in full:** !`cat "${CLAUDE_SKILL_DIR}/prompt.md"` (If the block above came back empty or errored, read `prompt.md` in this skill folder — it sits beside this `SKILL.md` — and follow that.) As you follow it, adapt for the fact that you're a Claude Code skill, not a pasted prompt: - **You're already invoked** — skip its "How to use / paste this" preamble. The field report(s) are `$ARGUMENTS` below (plus any attached files — an error log, a screenshot description, the file the reader was working in). Read the guide's `guide/` files yourself to place the report. - **You have file tools here** — **append the entry to `guide/feedback-log.md` on disk**, rather than only printing a fenced block. Create the ledger from `templates/feedback-log.md` if it's missing. - **Log-only — touch nothing else.** Do **not** edit step files, `status.md`, `decision-log.md`, or the guide `README.md`. The only file this skill writes is `guide/feedback-log.md`. - **Locate to log, not to fix.** Search the guide to fill **Where** accurately; do not edit the step you find. - When a real fix is warranted, hand off to the sibling **skill** `/report-issue` — say so; don't fix here. Field report(s) / args: ``` $ARGUMENTS ``` **Gate:** this skill captures, it does not repair — append to `guide/feedback-log.md` and change nothing else; one entry per distinct piece of frict