Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
Pulls full in-context user feedback tickets through the Produck MCP server and turns them into an aligned product change instead of a guess.
Install Produck Feedback To Build
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tryproduck/produck-skills produck-feedback --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/produck-feedback .claude/skills/produck-feedback && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .claude/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedbackType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tryproduck/produck-skills produck-feedback --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/produck-feedback .agents/skills/produck-feedback && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .agents/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tryproduck/produck-skills produck-feedback --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/produck-feedback .cursor/skills/produck-feedback && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .cursor/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tryproduck/produck-skills.git --path skills/produck-feedback--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tryproduck/produck-skills produck-feedback --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/produck-feedback .gemini/skills/produck-feedback && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .gemini/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tryproduck/produck-skills produck-feedbackInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/produck-feedback .github/skills/produck-feedback && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .github/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tryproduck/produck-skills --skill produck-feedback -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tryproduck/produck-skills produck-feedback --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tryproduck/produck-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/produck-feedback .opencode/skills/produck-feedback && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "produck-feedback" agent skill from https://github.com/tryproduck/produck-skills/tree/main/skills/produck-feedback into .opencode/skills/produck-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "produck-feedback", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
produck-feedback- GitHub stars
- 511
- Token cost
- ~1k tokens
- SKILL.md length
- 456 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Pulls full in-context user feedback tickets through the Produck MCP server and turns them into an aligned product change instead of a guess.
- Works in 4 steps: What this connects to → The two MCP tools → The operating loop → …
- Fixing a bug or gap a user reported through Produck
- SKILL.md covers 1. What this connects to, 2. The two MCP tools, 3. The operating loop and 4. Setup
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill drives the Produck MCP server's two tools to turn real user feedback into a build. One tool returns lightweight, paginated ticket summaries filtered by domain, while the other loads one ticket's full context - typed and transcribed notes, a reconstructed snapshot of the page the user was looking at, markers showing exactly what they pointed at, a timeline of what they did beforehand, and a generated design doc when Produck has already produced one.
The operating loop always loads the full ticket before building anything, since the skill treats acting on a summary alone as the mistake it exists to prevent: a ticket id can come from a search result, a pasted URL, or the user naming it directly. If the Produck MCP server isn't connected yet, it points to a companion reference covering how to connect it and mint a token first.
It triggers on phrases like fixing what users reported, a specific feedback ticket id, or building from a feedback queue, treating the richer session context as the reason to use real evidence instead of guessing at what a short complaint meant.
When your agent uses it
- Fixing a bug or gap a user reported through Produck
- Building a feature directly from a Produck feedback ticket
- Finding which open feedback tickets relate to a given page
Example prompts
- “Pull Produck feedback ticket 482 and build the fix it describes.”
- “Find feedback tickets about the checkout page and summarize them.”
- “Use my latest Produck feedback to write an aligned PRD.”
Requirements
- The Produck MCP server connected and authenticated
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9a699eb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
tryproduck.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Produck Feedback To Build loads about 1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tryproduck/produck-skills at commit 9a699eb, republished under its Apache-2.0 licence (© tryproduck). 456 words, ~1,028 tokens.
Download SKILL.mdSave it as
.claude/skills/produck-feedback/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- produck-feedback
- description
- Use when acting on real user feedback — you have a Produck feedback ticket or URL, or the user wants to fix something users complained about or build a feature users asked for. Pulls full feedback context through the Produck MCP and drives a feedback → aligned PRD → build loop. Triggers on "fix what users reported", a feedback ticket id, "use my produck feedback", or building from a feedback queue.
- license
- Apache-2.0
- metadata.author
- produck
- metadata.version
- 1.0.0
Building from Produck feedback
Purpose: Turn real, in-context user feedback into shipped fixes. This skill drives the Produck MCP — it tells the agent how to find the right feedback, load the full context behind it, and convert that context into an aligned change instead of a guess.
Requires the Produck MCP server connected. If
search_feedback/get_feedbackare not available, seereferences/connect-mcp.mdto connect it and mint a token first.
1. What this connects to
Produck captures feedback in the user's own session, so a ticket is far richer than a text complaint. Each ticket can carry:
- Written and spoken feedback — the user's typed note plus any voice transcription.
- Reconstructed page HTML — a static snapshot of the exact page the user was looking at.
- Annotation markers — the specific elements/regions the user pointed at.
- Session activity — a timeline of what the user did leading up to the feedback.
- A generated design doc — Produck's own first-pass analysis of the issue, when present.
The job of this skill is to pull that context and use all of it, not just the title.
2. The two MCP tools
The server is named produck (tools may appear prefixed, e.g. mcp__produck__search_feedback).
search_feedback — find relevant tickets
Returns lightweight summaries; use it to locate tickets, then load full context with get_feedback.
| Input | Type | Notes |
|---|---|---|
domain | string, optional | Filter to one website domain. |
limit | int 1–50, optional | Defaults to 20. |
cursor | string, optional | Pagination cursor from a previous call. |
Returns { items, nextCursor, count } — each item a summary (id, domain, page URL, created-at,
annotation count, source). Page with cursor until nextCursor is null when you need the full set.
Show full SKILL.md (188 more words)Show less
get_feedback — load one ticket in full
| Input | Type | Notes |
|---|---|---|
feedbackId | string, required | The ticket id (from a search_feedback item, a URL, or the user). |
Returns the full ticket: written/spoken feedback, reconstructed HTML, annotations, session activity,
and the design doc when present. Always get_feedback before building — never act on a summary alone.
3. The operating loop
search_feedback → find the relevant ticket(s) (filter by domain, page as needed)
get_feedback → load ONE ticket's full context
user-alignment → turn the ticket into an agent-executable PRD (do not skip)
build → implement the fix / high-fidelity mockup
verify → check the change against the ticket's annotations + design doc- Do not jump from a raw ticket straight to code. A ticket is a user request, not a spec. Hand
it to the
user-alignmentskill first to produce an aligned PRD — interpreted intent, scope, non-goals, acceptance criteria — then build from that. The two skills are designed to compose. - Ground every decision in the captured context. Use the reconstructed HTML and annotation markers to locate the exact elements involved; use the session activity to understand what the user was doing; use the design doc as a starting hypothesis, not the final answer.
- Close the loop. When you finish, verify the result against the annotations and the stated outcome — the same ticket is your acceptance check.
4. Setup
To connect the MCP, choose the install path for your agent and mint a token — see
references/connect-mcp.md.
© tryproduck, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/produck-feedback of tryproduck/produck-skills.
- SKILL.md
- references/connect-mcp.md
Open the folder on GitHubat commit 9a699eb
Compare with similar skills
Produck Feedback To Build next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Produck Feedback To Build this skilltryproduck/produck-skills | 511 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | — | ~5.7k | Automated safety check: Pass | MIT | |
| Rhesisrhesis-ai/rhesis | 397 | — | ~1.2k | Automated safety check: Pass | Proprietary | |
| Execute Fleetanombyte93/prd-taskmaster | 605 | — | ~2.2k | Automated safety check: Notes | MIT | |
| Discovery Synthesisandreaskelm/pm-brain | 234 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Tapd Product DiscoveryTencentBlueKing/bk-bcs | 840 | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Rhesis
rhesis-ai/rhesis
Design, run, and analyze AI test suites on Rhesis — explore endpoints, build test foundations from a spec, create requirements and metrics, execute tests, and analyze results.
Execute Fleet
anombyte93/prd-taskmaster
Phase execution skill for licensed Atlas Fleet runs. An agent skill from anombyte93/prd-taskmaster.
Discovery Synthesis
andreaskelm/pm-brain
Plan customer discovery, turn interview snapshots into synthesis and evidence-based opportunities, build or update an Opportunity Solution Tree, map jobs and segments, and design RAT tests for the…
Tapd Product Discovery
TencentBlueKing/bk-bcs
A skill your agent uses when work starts before a complete PRD exists, including 产品前置, 产品调研, 用户调研, 竞品分析, PRD, 原型, 想法建单, 老板需求, 需求来源, 产品父单, 角色拆单, 设计子单, 前端子单, 后端子单, 页面原型 Spec, BKUI 原型, HTML 原型, 原型评审…
Ralph
opentabs-dev/opentabs
Plan work and generate ralph task files for autonomous execution.
More from tryproduck/produck-skills
Website Taste Pass
tryproduck/produck-skills
Runs a category-first visual audit of a website, then a decisive design pass that raises credibility and conversion clarity, verified with screenshots instead of subjective opinion.
User Alignment and Agent-Ready PRDs
tryproduck/produck-skills
Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.
Related
Works with
Categories
Questions about Produck Feedback To Build
What does Produck Feedback To Build do?
Pulls full in-context user feedback tickets through the Produck MCP server and turns them into an aligned product change instead of a guess. This skill drives the Produck MCP server's two tools to turn real user feedback into a build. One tool returns lightweight, paginated ticket summaries filtered by domain, while the other loads one ticket's full context - typed and transcribed notes, a reconstructed snapshot of the page the user was looking at, markers showing exactly what they pointed at, a timeline of what they did beforehand, and a generated design doc when Produck has already produced one.
When should I use Produck Feedback To Build?
Produck Feedback To Build fits situations like: fixing a bug or gap a user reported through Produck; building a feature directly from a Produck feedback ticket; finding which open feedback tickets relate to a given page.
How do I install Produck Feedback To Build in Claude Code?
Run `npx skills add tryproduck/produck-skills --skill produck-feedback -a claude-code`. Or copy the skill folder (skills/produck-feedback in tryproduck/produck-skills) into .claude/skills/produck-feedback in your project. Claude Code loads it when a task matches its description.
How do I install Produck Feedback To Build in Codex?
Run `npx skills add tryproduck/produck-skills --skill produck-feedback -a codex`. Or copy the skill folder (skills/produck-feedback in tryproduck/produck-skills) into .agents/skills/produck-feedback in your project. Codex loads it when a task matches its description.
Can I use Produck Feedback To Build in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tryproduck/produck-skills --skill produck-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/produck-feedback, .gemini/skills/produck-feedback, .github/skills/produck-feedback and .opencode/skills/produck-feedback in your project.
What does Produck Feedback To Build need to run?
SKILL.md names no scripts, command-line tools or credentials: Produck Feedback To Build is instructions for the agent only. Our summary lists: The Produck MCP server connected and authenticated.
Does Produck Feedback To Build access the network?
SKILL.md names 1 domain. As links in the text: tryproduck.com. This is read from the text; nothing was executed.
Is Produck Feedback To Build safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Produck Feedback To Build use?
Produck Feedback To Build is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Produck Feedback To Build use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 628 tokens, read only when the agent opens those files.
What are the alternatives to Produck Feedback To Build?
Skills that share tags, products or a category with Produck Feedback To Build: Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), Rhesis (rhesis-ai/rhesis, 397 stars), Execute Fleet (anombyte93/prd-taskmaster, 605 stars) and Discovery Synthesis (andreaskelm/pm-brain, 234 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Produck Feedback To Build?
tryproduck (a GitHub organization) maintains it in tryproduck/produck-skills, which has 511 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 14, 2026.
Source: tryproduck/produck-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.