Capture feedback where it happens. Ship it where you already work.

Skiff is the feedback-to-code loop — bugs, ideas, and product notes captured in your app, then surfaced in Cursor, Codex, or Claude Code through native MCP plugins. No copy-paste. No vague prompts.

Bugs, ideas, and QA notes — one click, full context
MCP plugins for Cursor, Codex, and Claude Code
Copy one ticket or multi-select a cluster into your agent

Start free See how it works in your editor

The 🪦 old way to build with AI

Spot a bug, idea, or note → screenshot it → post in Slack → someone writes a ticket → engineer asks “which page?” → paste into Cursor → agent guesses from a vague prompt.

AI coding tools use your codebase as the source of truth, not how people actually experience your product.

The Skiff way

See feedback → capture in-app → structured ticket with signals attached → Fix SKF-142 in Cursor. Agent starts with evidence, not a Slack thread.

AI coding is only as good as the ticket. Skiff closes the loop between feedback and code.

Relaying feedback (now)6 steps

Spot feedback in productHuman

Screenshot → SlackHuman

Write ticket / promptHuman

Re-describe for agentHuman

Agent guessesMachine

Review + shipHuman

Signals

Feature ideas

In-app notes

Screenshots

Session video

Console errors

Routes + browser

Changed files

QA checklists

PR comments

The vibe coding tax

Stop relaying feedback twice.

A bug, an idea, or a rough note shows up in your product — then someone re-describes it in Slack, Linear, or a chat prompt. Context dies in translation. Skiff captures it where it happens, structures it once, and makes it available in the tools you already use.

Without Skiff

Bugs, ideas, and notes trapped in Slack or email
QA and UX feedback with no URL, build, or repro
Tickets copied from messages—still missing proof
Engineers asking “which page?” and “which user?”
Agents guessing because the ticket is vague
Backlog grows while context stays fuzzy

With Skiff

In-app capture: screenshot, URL, environment, notes
Structured triage: title, repro, severity, priority
One source of truth your product team can trust
MCP plugins bring tickets into Cursor, Codex, or Claude Code
Fix from chat or copy context—no re-describing the report
Review, edit, merge—ship with confidence

Fix from chat

Skiff doesn't replace your editor. It feeds it.

Install the Skiff MCP server once. Use the native plugin in Cursor, Codex, or Claude Code. List tickets, reference by ID, or paste copied context — your agent starts with evidence, not a vague thread.

No more copy-pasting feedback into chat. Ask Fix SKF-142 and the full brief is already attached.

Cursor — skiff-websiteSkiff MCP

skiff-websiteLocalmain

You

@skiff list open tickets

Skiff MCP

SKF-142Checkout button mobileREADY · 8 users

SKF-138Onboarding dismissQUEUED · 4 users

SKF-131Settings page flashREADY · 12 users

You

Fix SKF-142. Include repro, route, screenshot, and acceptance criteria.

Ask Skiff or reference a ticket…Send

Inside the loop

Watch feedback become code

Five steps from in-product feedback to a merged branch — the same loop in beta, QA, or production.

01
Capture
Bugs, ideas, feature asks, and QA notes land in-app with screenshot, URL, and environment attached.
02
Triage
Skiff turns each report into structured work: summary, repro, severity, and priority.
03
Fix in your editor
Use the Skiff MCP plugin in Cursor, Codex, or Claude Code. Reference a ticket by ID, or paste copied context from the inbox.
Cursor — skiff-websiteSkiff MCP
You
@skiff list open tickets
Skiff MCP
SKF-142Checkout button mobileREADY · 8 users
SKF-138Onboarding dismissQUEUED · 4 users
SKF-131Settings page flashREADY · 12 users
You
Fix SKF-142. Include repro, route, screenshot, and acceptance criteria.
Ask Skiff or reference a ticket…Send
04
Review
Your team inspects the branch in GitHub and keeps control. Skiff accelerates the start, not the merge.
05
Merge
Ship when the fix is reviewed. Same bar as today, less time getting there.

Everything you expect from an AI coding workflow,
but with the missing product context.

In your editor

Install the Skiff MCP plugin in Cursor, Codex, or Claude Code. List tickets, reference by ID, or ask your agent to fix a report — full context attached, no dashboard required.

Cursor — skiff-websiteSkiff MCP

skiff-websiteLocalmain

You

@skiff list open tickets

Skiff MCP

SKF-142Checkout button mobileREADY · 8 users

SKF-138Onboarding dismissQUEUED · 4 users

SKF-131Settings page flashREADY · 12 users

You

Fix SKF-142. Include repro, route, screenshot, and acceptance criteria.

Ask Skiff or reference a ticket…Send

Skiff instrumentation for product feedback

Give the agent the ticket you wish you had — evidence attached from capture through triage to your editor.

Capture where it happens

Bugs, ideas, and product notes — one click in your app with screenshot, route, environment, and context attached.

Capture in your product

SReport feedback

Idea: let users save their plan selection before checkout. Also seeing a mobile layout bug on Safari.

/checkoutScreenshotiOS 18

Submit capture

Multi-select. Copy once. Fix in batch.

Select related reports and copy the full cluster into your agent — screenshots, routes, user counts, and repro in one shot.

Inbox — tickets ready for your agent

3 copied

Copy to agent3 selected

SKF-142

Checkout button disappears on mobile

READY

8 users · screenshot, console

SKF-138

Beta user cannot dismiss onboarding

QUEUED

4 users · note, route

SKF-131

Settings page flashes blank

READY

12 users · session video

SKF-127

Add bulk export for usage data

NEW

6 users · idea, note

MCP plugins, not another platform

Native plugins for Cursor, Codex, and Claude Code. Stay in your editor — Skiff feeds it structured context.

Cursor

List tickets, copy context, fix from chat

Codex

Pull structured repro and screenshots into a task

Claude Code

Reference tickets and batch related reports

Your team keeps control

Skiff structures the input and keeps evidence attached. You review and merge in GitHub like always.

CaptureIn your product

TriageAI-structured brief

FixIn Cursor / Codex / Claude Code

MergeIn GitHub, your bar

What Skiff captures

Every report ships with the context agents need — no reformatting, no chasing people for screenshots.

EVIDENCE

ScreenshotsSession videoConsole errors

CONTEXT

Routes + browserIdeas + notesQA checklists

Works in the tools you already use

Install the Skiff MCP server once. Each agent gets a native plugin — no deep integration, no control plane to babysit.

Cursor

List tickets, copy context, fix from chat.

Codex

Pull structured repro and screenshots into a task.

Claude Code

Reference tickets and batch related reports.

Turn feedback into fixes

Capture bugs, ideas, and feedback where they happen. Ship from Cursor, Codex, or Claude Code with a brief that is ready to build.

Start free See how it works in your editor

FAQ

Skiff is a feedback-to-code workspace for AI-native product teams. It captures bugs, ideas, and product feedback with context where they happen and turns them into structured tickets your coding agent can actually use.

Skiff ships an MCP server with a plugin for each agent. Install once, then use native tools in chat — list tickets, copy context, reference by ID. Skiff doesn't run your agent or open branches for you; it gives your agent the brief.

No. Skiff sits between product feedback and the tools you already use. It creates better tickets and makes them available in your editor — your issue tracker and GitHub workflow stay the same.

Yes. Multi-select related reports in the inbox and copy the full cluster — screenshots, routes, user counts, and repro — into your agent in one shot. Great for sprint-sized batches of related feedback.

Founders, product engineers, QA teams, and beta-heavy teams shipping with AI coding tools.

A repro, screenshot or recording, route, environment, impact, suggested files, constraints, and clear done criteria. That is the Skiff brief.