Software Development
Troubleshooting Guide Writer
Troubleshooting Guide Writer turns product documentation & onboarding material into a draft package with a concrete symptom-to-cause tree, diagnostic command path, and known-fix escalation ladder. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for feature, API, setup, or onboarding source, target reader and first-success moment, and known errors, prerequisites, and support paths up front, then organizes the output around troubleshooting, guide, product, documentation, and onboarding. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Troubleshooting Guide Writer is scoped to the Product Documentation & Onboarding workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
Troubleshooting Guide Writer — Sample Brief
Headline
Builds a product documentation artifact for troubleshooting guide writer work, turning feature, API, setup, or onboarding source, target reader and first-success moment, and known errors, prerequisites, and support paths into symptom-to-cause tree, diagnostic command path, and known-fix escalation ladder. In this example, Northbeam Analytics needs a reviewer-ready draft package built from supplied notes, constraints, and approval context. The output is a concrete draft package: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| feature, API, setup, or onboarding source | Northbeam Analytics needs a reviewer-ready draft package built from supplied notes, constraints, and approval context. | Provided |
| target reader and first-success moment | Three representative examples from the current workflow | Reviewed |
| known errors, prerequisites, and support paths | Approval threshold and final reviewer | Confirm |
| publishing owner and maintenance cadence | Product Documentation & Onboarding owner and downstream audience | Ready |
Troubleshooting Evidence Model
| Field | What must be captured | Review consequence |
|---|---|---|
| Troubleshooting signal | Anchor the result in troubleshooting, guide, and writer evidence from the supplied material. | Treat as draft until symptom-to-cause tree is source-backed. |
| Symptom To Cause Tree | Separate Troubleshooting signal, Guide judgment, and Writer action before drafting. | Escalate when troubleshooting evidence is missing or contradicted. |
| Diagnostic Command Path | Name the review question that makes Troubleshooting Guide Writer different from the rest of Product Documentation & Onboarding. | Reviewer resolves known-fix escalation ladder before final use. |
Troubleshooting Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Troubleshooting depth | Anchor the result in troubleshooting, guide, and writer evidence from the supplied material. | Keep, revise, or ask a targeted follow-up |
| Guide boundary | Separate Troubleshooting signal, Guide judgment, and Writer action before drafting. | Confirm this is not a renamed adjacent bundle skill |
| Writer handoff | Name the review question that makes Troubleshooting Guide Writer different from the rest of Product Documentation & Onboarding. | Assign the owner decision before final use |
Troubleshooting Guide Writer Work Map
Troubleshooting Guide Writer focus areas
Draft Draft Package
| Troubleshooting signal | Symptom To Cause Tree | Diagnostic Command Path | Known Fix Escalation Ladder | Guide decision |
|---|---|---|---|---|
| Troubleshooting | symptom-to-cause tree | diagnostic command path | known-fix escalation ladder | Keep if source-backed |
| Guide | symptom-to-cause tree | diagnostic command path | Troubleshooting evidence is missing or contradicted. | Revise missing evidence |
| Product | Anchor the result in troubleshooting, guide, and writer evidence from the supplied material. | Separate Troubleshooting signal, Guide judgment, and Writer action before drafting. | known-fix escalation ladder | Assign owner decision |
Use now
Troubleshooting Guide Writer
Best when product documentation & onboarding work needs a concrete draft package.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. Companies referenced are fictional and used recurringly across sample outputs.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Product Documentation & Onboarding
Bundle price: $55. Compare this skill with the full workflow bundle or Pro access.
Best for
Support engineers and DevRel writing a troubleshooting guide — symptom-to-cause tree, diagnostic commands, and a known-fix escalation ladder. Most useful when the same support issues recur and a self-serve guide would deflect tickets.
Not ideal for
Novel issues with no established fix, and incident response for a live outage. It documents the known paths — a maintainer should confirm the diagnostics and fixes are current before publishing.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short setup in the repository or workspace where the skill will run. Some coding familiarity helps for implementation-heavy outputs.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.