From docs-tools
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.
npx claudepluginhub redhat-documentation/redhat-docs-agent-tools --plugin docs-toolsThis skill is limited to using the following tools:
Step skill for the docs-orchestrator pipeline. Follows the step skill contract: **parse args → do work → write output**.
Orchestrates documentation workflows from YAML step lists, running skills sequentially with progress state, iterations, confirmations, and JIRA/PR integration.
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.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
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)
$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)<base-path>/planning/plan.md
Requires JIRA_AUTH_TOKEN and JIRA_EMAIL in the environment (typically sourced from ~/.env).
Run the create-jira-ticket script:
bash scripts/create-jira-ticket.sh "$TICKET" "$PROJECT" "${BASE_PATH}/planning/plan.md"
The script handles all steps:
scripts/md2wiki.py for markdown → wiki conversion[ccs] Docs - prefixThe 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.