Trace a customer-reported problem through your code in read-only mode
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Use cases
Show all 6Show fewer
Methods
Open every related repo, switch the assistant to read-only mode, trace back from the exact symptom, then classify the cause
Steps
- Open all repos that could plausibly touch the symptom in one multi-root workspace (frontend, backend, docs).
- Switch to a read-only or ask mode.
- Prompt: "A customer reports: [exact symptom, for example 'this button is disabled']. Trace backward from this UI/behavior through the code and docs. List the conditions that produce it, with file references, and say which repo each comes from."
- After you know the cause, decide whether it is expected behavior, a bug or a docs gap.
- Use it when you support a product and can open its code and docs. Read-only mode keeps the assistant from changing anything while it investigates.
- Note: Steps from OpenTacit's technique page, credited to Kody Fisher and Zach Hudson (CC BY 4.0).
Run this method with your agent
Download .mdCopied 0
--- name: "trace-support-issue-read-only-method" description: "Use when you need to Trace a customer-reported problem through your code in read-only mode. Open every related repo, switch the assistant to read-only mode, trace back from the exact symptom, then classify the cause" --- # Open every related repo, switch the assistant to read-only mode, trace back from the exact symptom, then classify the cause Job: [Trace a customer-reported problem through your code in read-only mode](https://aiagents.org/canai/trace-support-issue-read-only) ## Need - AI agent ## Steps 1. Open all repos that could plausibly touch the symptom in one multi-root workspace (frontend, backend, docs). 2. Switch to a read-only or ask mode. 3. Prompt: "A customer reports: [exact symptom, for example 'this button is disabled']. Trace backward from this UI/behavior through the code and docs. List the conditions that produce it, with file references, and say which repo each comes from." 4. After you know the cause, decide whether it is expected behavior, a bug or a docs gap. 5. Use it when you support a product and can open its code and docs. Read-only mode keeps the assistant from changing anything while it investigates. 6. Note: Steps from OpenTacit's technique page, credited to Kody Fisher and Zach Hudson (CC BY 4.0). ## Credit Method author OpenTacit (Kody Fisher, Zach Hudson; CC BY 4.0) Source: https://opentacit.com/t/start-a-support-investigation-read-only-from-the-symptom/
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/trace-support-issue-read-only - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "trace-support-issue-read-only",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}