Skill

docs-workflow-create-jira

Creates linked JIRA documentation ticket from markdown plan via bash script and REST API. Checks existing links, handles public/private projects, converts MD to wiki markup.

Bash

Jira

npx claudepluginhub redhat-documentation/redhat-docs-agent-tools --plugin docs-tools

Configuration

Model: claude-haiku-4-5@20251001

Tool Access

This skill is limited to using the following tools:

ReadWriteBash

Preview

Step skill for the docs-orchestrator pipeline. Follows the step skill contract: **parse args → do work → write output**.

Supporting Assets

scripts/build-payload.pyscripts/create-jira-ticket.shscripts/extract-description.pyscripts/md2wiki.py

SKILL.md

Similar Skills

docs-orchestrator

Orchestrates documentation workflows from YAML step lists, running skills sequentially with progress state, iterations, confirmations, and JIRA/PR integration.

3 files10 tools

docs-tools

jira-create

Creates Jira epics, stories, and sub-tasks from jira-export-latest.md using MCP-Jira. Auto-generates export if missing. For converting drafts to tracked issues.

draft

using-superpowers

178.4k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars14

Parent Repo Forks11

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create JIRA Step

Step skill for the docs-orchestrator pipeline. Follows the step skill contract: parse args → do work → write output.

Unlike other step skills, this skill does not dispatch an agent. It runs scripts/create-jira-ticket.sh directly.

Output: null (produces a JIRA URL, not a file)

Arguments

$1 — Parent JIRA ticket ID (required)

--base-path <path> — Base output path (e.g., .claude/docs/proj-123)

--project <PROJECT> — Target JIRA project key for the new ticket (required)

Input

<base-path>/planning/plan.md

Environment

Requires JIRA_AUTH_TOKEN and JIRA_EMAIL in the environment (typically sourced from ~/.env).

Execution

Run the create-jira-ticket script:

bash scripts/create-jira-ticket.sh "$TICKET" "$PROJECT" "${BASE_PATH}/planning/plan.md"

The script handles all steps:

Check for existing link — if a "Document" link already exists on the parent ticket, exits early

Check project visibility — unauthenticated probe to determine public vs private

Extract description — pulls JTBD sections from the plan, appends dated footer

Convert to JIRA wiki markup — calls scripts/md2wiki.py for markdown → wiki conversion

Create JIRA ticket — POST to JIRA REST API with [ccs] Docs - prefix

Link to parent — creates a "Document" issue link (singular, not "Documents")

Attach plan — attaches the full plan file (private projects only)

The script prints the JIRA URL on success (e.g., https://redhat.atlassian.net/browse/DOCS-456).

This step does not write an output file. The progress file records output: null for this step.