kb-articlelisted

# /kb-article > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Draft a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. Structures the content for searchability and self-service. ## Usage ``` /kb-article <resolved issue, ticket reference, or topic description> ``` Examples: - `/kb-article How to configure SSO with Okta — resolved this for 3 customers last month` - `/kb-article Ticket #4521 — customer couldn't export data over 10k rows` - `/kb-article Common question: how to set up webhook notifications` - `/kb-article Known issue: dashboard charts not loading on Safari 16` ## Workflow ### 1. Understand the Source Material Parse the input to identify: - **What was the problem?** The original issue, question, or error - **What was the solution?** The resolution, workaround, or answer - **Who does this affect?** User type, plan level, or configuration - **How common is this?** One-off or recurring issue - **What article type fits best?** How-to, troubleshooting, FAQ, known issue, or reference (see article types below) If a ticket reference is provided, look up the full context: - **~~support platform**: Pull the ticket thread, resolution, and any internal notes - **~~knowledge base**: Check if a similar article already exists (update vs. create new) - **~~project tracker**: Check if there's a related bug or feature request ### 2. Dra