kcs

Convert Jira bug reports and workarounds into KCS Solution articles.

6|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/flightctl/ai-workflows --skill kcs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kcs
Source: https://github.com/flightctl/ai-workflows/tree/main/kcs
Command: npx skills add https://github.com/flightctl/ai-workflows --skill kcs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered bug and workaround details from Jira and the user into a consistent KCS Solution article that can be reviewed and published by support.

Core Features & Use Cases

  • Context-driven gathering: Collects Jira ticket details and merges user-provided symptoms, workaround steps, diagnostics, and any root-cause information.
  • Template-based drafting: Produces a structured KCS Solution in Markdown with the required sections and writing guidance.
  • Checklist validation: Checks the draft against the KCS validation checklist and auto-fixes minor style/format issues.
  • Support-engineer handoff: Creates a copy-paste handoff message with the validated draft ready for portal publishing.
  • Portable artifacts: Writes phase outputs to .artifacts/kcs/{issue-key}/ for easy reuse and review.

Quick Start

Tell the agent: Provide a Jira issue key (or link) and the known workaround steps, then run /gather, /draft, /validate, and /handoff to generate and validate the KCS Solution article.

Frequently Asked Questions about kcs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a Jira bug report into a KCS Solution article?▼

To convert a Jira bug report into a KCS Solution article, provide the issue key and workaround steps. The workflow gathers context, drafts structured Markdown, validates against a checklist, and outputs a handoff message for support publication.

What is the process for validating a KCS article draft before support handoff?▼

Validating a KCS article draft involves checking the generated content against a KCS validation checklist and automatically fixing minor style and formatting issues to ensure it meets publication standards before handoff.

Can I use my own Markdown template for drafting KCS articles from known issues?▼

Yes, the drafting process is template-based, producing a structured KCS Solution in Markdown with required sections and writing guidance to ensure consistency for known issues and workarounds.

How do I generate a support handoff message for a validated KCS article?▼

Generating a support handoff message is accomplished by running the handoff command after validation, which creates a copy-paste formatted output containing the validated KCS Solution draft ready for portal publishing.

Where are the generated KCS drafts and workflow artifacts stored?▼

Generated KCS drafts and workflow artifacts are persisted locally in the `.artifacts/kcs/{issue-key}/` directory, ensuring easy reuse and review across the structured multi-phase execution process.