check-feedbacklisted

# Check Feedback - PMF Signals from Rejection Feedback A read-only skill that surfaces **product/pricing/business-model** signals from rejection feedback recorded by `/check-responses`. Use this for PMF reflection — questions like "is there a missing feature people keep asking for?" or "are we losing to a specific competitor?". This skill is **not** for sales tactics. Tactical signals from rejections (when to recontact, who to redirect to, which industries to deprioritize) are consumed automatically by `/evaluate` in the daily cycle. Do not use `/check-feedback` to drive operational decisions. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## Steps ### 1. Verify Arguments - Project ID: `$0` (required) Return an error if `$0` is empty. ### 2. Fetch Two Windows in Parallel Call `mcp__plugin_leadace_api__get_rejection_feedback_summary` twice in parallel, both with `scope: "pmf"`: 1. `projectId: "$0"`, `windowDays: 30`, `scope: "pmf"` -> recent 2. `projectId: "$0"`, `scope: "pmf"` (no `windowDays`) -> all-time If the tool returns "Project not found", instruct the user to run `/leadace` first and abort. With `scope: "pmf"` the server filters to PMF-relevant reasons only and computes `total` + `percentage` within the PMF subset. `recontactWindows` is returned with all five buckets at `{count: 0, samples: []}` and