Purpose
Turn a product limitation or open bug into a ranked set of practical workarounds — each written so a support associate can either walk the customer through it live or paste it into a reply. Solves the "there's no feature for that yet, and I don't know what to tell them" moment that stalls tickets and drives escalations.
When to Use
Invoke this skill when the user asks to:
- Find a workaround for a feature the product doesn't have yet
- Help a customer accomplish a goal blocked by a confirmed bug
- Respond to a "can your product do X?" ticket where the answer is "not directly"
- Buy time on a ticket while a fix or feature request is in the backlog
- Reduce escalations by offering the customer a path forward instead of "I'll file that"
- Draft a customer-facing reply that offers alternatives without overpromising
Inputs Required
Before starting, collect:
- The limitation or bug: What the product can't do, or the specific broken behavior
- What the customer is trying to accomplish: Their actual end goal, not just the feature they asked for
- Product surface area: Which parts of the product exist and are relevant (features, integrations, exports, API, settings)
- Customer technical comfort: Non-technical / general business user / technical / developer
- Constraints: Anything off the table — no third-party tools, no code, no plan upgrade, data privacy limits
- Bug status (if applicable): Confirmed / under investigation / fix ETA known or unknown
- Plan/tier (if relevant): Whether certain features or integrations are available on their plan
If technical comfort isn't provided, assume general business user and keep steps click-based. If plan tier is unknown, flag any workaround that may require a specific tier.
Instructions
Step 1: Reframe to the Underlying Goal
Separate the requested feature from the job the customer is trying to get done. A workaround succeeds if it achieves the goal, not if it recreates the feature. Write one sentence: "The customer actually needs to ___, and the missing feature was just one way to do that." Generate workarounds against the goal, not the feature.
Step 2: Generate 5-8 Workarounds Across These Approaches
Produce candidates by working through each approach below. Not every approach yields a viable option — skip any that don't fit, but aim for coverage across at least four.
Approach A — Existing feature repurposed Use a current feature in a way it wasn't primarily designed for (tags as status, a custom field as a flag, a saved view as a report). Lowest risk, no external dependencies.
Approach B — Multi-step manual process Chain existing actions to reach the goal (export → edit → re-import; duplicate → modify; filter → bulk action). Higher effort but fully in-product.
Approach C — Export / import bridge Move data out via CSV/export, transform it, and bring the result back or use it elsewhere. Good when the gap is in reporting, formatting, or bulk changes.
Approach D — Integration or native connector Use an existing integration (Zapier, native connectors, calendar/email sync) to fill the gap. Flag any that require a specific plan tier.
Approach E — API or automation For technical/developer customers only: an endpoint, webhook, or script that accomplishes the goal programmatically. Skip entirely for non-technical customers.
Approach F — External free/low-cost tool A lightweight outside tool (spreadsheet, free form builder, scheduling tool) used alongside the product. Only if constraints allow third-party tools.
Approach G — Interim behavioral / process change A change in how the customer's team operates that sidesteps the limitation until a fix ships (naming convention, shared doc, manual cadence).
Step 3: Detail Each Workaround
For every option, provide:
- Name: A short, plain-language label
- What it does: One sentence on how it reaches the goal
- Steps: Numbered, click-level instructions matched to the stated technical comfort
- Effort: Low / Medium / High (setup time + ongoing maintenance)
- Goal coverage: Full / Partial — and if partial, exactly what it does not solve
- Watch-outs: Data risk, tier requirement, breakage if the bug behaves unexpectedly, or anything to warn the customer about
Step 4: Rank the Options
Order the workarounds best-to-worst using this priority: (1) full goal coverage, (2) lowest effort, (3) no external dependencies, (4) matches customer's technical comfort. Name the single recommended option and say why in one sentence.
Step 5: Draft the Customer-Facing Reply
Write a paste-ready message that: acknowledges the limitation honestly, presents the top 1-2 workarounds in the customer's language (not internal jargon), sets accurate expectations (never promise a fix date unless one is confirmed), and offers a next step. If a bug fix or feature request exists, offer to link the ticket to their account for updates.
Output Format
- Structure: Goal reframe → ranked workaround list → recommended option → customer-facing reply
- Length: 700–1,100 words
- Format: Numbered/ranked list for workarounds with labeled sub-fields; the customer reply as a distinct quoted block
- Sections: Underlying Goal → Workaround Options (ranked, 5-8) → Recommended Option → Customer-Ready Reply
- Tone: Internal analysis is direct and practical; the customer reply is warm, honest, and jargon-free — no overpromising, no blaming the roadmap
Quality Checklist
Before delivering output, verify:
- [ ] 5-8 workarounds are present and drawn from at least four different approaches
- [ ] Every workaround has all six sub-fields (name, what it does, steps, effort, goal coverage, watch-outs)
- [ ] Step instructions match the customer's stated technical comfort — no API steps for non-technical users
- [ ] Options are ranked, with one clearly recommended and a reason given
- [ ] The customer reply sets no fix/ETA promise unless a confirmed date was provided
- [ ] Any workaround requiring a specific plan tier or third-party tool is flagged against the stated constraints
Notes
- The reframe in Step 1 is where most value is created — customers often ask for a specific feature when a simpler path already exists.
- "Partial coverage" is honest and useful; label it clearly rather than overselling a workaround that leaves a gap.
- For confirmed bugs, a good workaround plus a linked ticket for updates prevents most re-contacts and escalations.
- If no viable workaround exists, say so plainly in the reply and pivot to what you can do: escalate, log the request with weight, or set a realistic follow-up.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills