TanStack · LadyBluenotes · Jun 16, 2026 · Jun 16, 2026 · Jun 16, 2026
diff --git a/.changeset/pretty-sloths-switch.md b/.changeset/pretty-sloths-switch.md
@@ -0,0 +1,5 @@
+---
+'@tanstack/intent': patch
+---
+
+Remove the unused feedback APIs, bundled feedback meta-skill, tests, and docs references.
diff --git a/docs/getting-started/quick-start-consumers.md b/docs/getting-started/quick-start-consumers.md
@@ -107,12 +107,3 @@ You can also check if any skills reference outdated source documentation:
 npx @tanstack/intent@latest stale
 ```
 
-## 5. Submit feedback (optional)
-
-After using a skill, you can submit feedback to help maintainers improve it:
-
-```bash
-npx @tanstack/intent@latest meta feedback-collection
-```
-
-This prints a skill that guides your agent to collect structured feedback about gaps, errors, and improvements.
diff --git a/packages/intent/README.md b/packages/intent/README.md
@@ -117,8 +117,6 @@ npx @tanstack/intent@latest setup
 
 The real risk with any derived artifact is staleness. `npx @tanstack/intent@latest stale` flags skills whose source docs have changed, generated skills that drift from `_artifacts`, and public workspace packages missing coverage. CI templates catch drift before it ships.
 
-The feedback loop runs both directions. `npx @tanstack/intent@latest feedback` lets users submit structured reports when a skill produces wrong output — which skill, which version, what broke. That context flows back to the maintainer, and the fix ships to everyone on the next package update. Every support interaction produces an artifact that prevents the same class of problem for all future users — not just the one who reported it.
-
 ## CLI Commands
 
 | Command                                            | Description                                         |
@@ -131,7 +129,6 @@ The feedback loop runs both directions. `npx @tanstack/intent@latest feedback` l
 | `npx @tanstack/intent@latest validate [dir]`       | Validate SKILL.md files                             |
 | `npx @tanstack/intent@latest setup`                | Copy CI templates into your repo                    |
 | `npx @tanstack/intent@latest stale [dir] [--json]` | Check skills for version drift                      |
-| `npx @tanstack/intent@latest feedback`             | Submit skill feedback                               |
 
 ## License
 

diff --git a/packages/intent/meta/domain-discovery/SKILL.md b/packages/intent/meta/domain-discovery/SKILL.md
@@ -572,7 +572,7 @@ Include the full draft domain_map.yaml in your message so the maintainer
 can review it. Also include a checklist of all docs files you read.
 
 **── STOP ── Do not proceed to Phase 4 until the maintainer has
-reviewed the draft and responded. Their feedback on the draft informs
+reviewed the draft and responded. Their response to the draft informs
 the detail interview questions.**
 
 ---

diff --git a/packages/intent/meta/feedback-collection/SKILL.md b/packages/intent/meta/feedback-collection/SKILL.md
diff --git a/packages/intent/meta/generate-skill/SKILL.md b/packages/intent/meta/generate-skill/SKILL.md
@@ -118,7 +118,7 @@ cannot already know:
 
 Before writing the skill body, search the library's GitHub repo for issues
 and discussions relevant to THIS skill's topic. This step is important for
-both initial generation and regeneration — community feedback reveals
+both initial generation and regeneration — issue discussions reveal
 failure modes that docs miss.
 
 **Search strategy:**
@@ -443,11 +443,4 @@ Output is consumed by all major AI coding agents. To ensure consistency:
 - Critical info at start or end of sections (not buried in middle)
 - Each SKILL.md is self-contained except for declared `requires`
 
----
-
-## Meta-skill feedback
-
-After generating all skills, run the `skill-feedback-collection` skill to
-capture feedback about the scaffolding process (domain-discovery,
-tree-generator, and generate-skill).
 ```
diff --git a/packages/intent/meta/tree-generator/SKILL.md b/packages/intent/meta/tree-generator/SKILL.md
@@ -702,7 +702,7 @@ Run when:
 - The library has released a new version
 - A maintainer reports skills produce outdated code
 - A changelog or migration guide has been published since skill creation
-- Feedback reports indicate skill content is inaccurate
+- Issue reports indicate skill content is inaccurate
 
 ### Step 1 — Detect staleness
 

diff --git a/packages/intent/src/commands/list.ts b/packages/intent/src/commands/list.ts
@@ -162,15 +162,6 @@ export async function runListCommand(
     console.log()
   }
 
-  console.log('Feedback:')
-  console.log(
-    '  Submit feedback on skill usage to help maintainers improve the skills.',
-  )
-  console.log(
-    '  Load: node_modules/@tanstack/intent/meta/feedback-collection/SKILL.md',
-  )
-  console.log()
-
   printWarnings(result.warnings)
   printNotices(result.notices, noticeOptions)
 }