From docs-tools
Generates documentation plan from requirements analysis including gap analysis, module specs, implementation order, and assembly structure. Dispatches docs-planner agent for JIRA tickets.
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 → dispatch agent → write output**.
Analyzes documentation requirements for JIRA tickets by dispatching requirements-analyst agent with PR URLs. Saves structured Markdown output for docs pipelines.
Analyzes software development requirements, breaks them into categorized actionable steps, and generates structured plans with TaskList.md in ./docs/. Useful before task implementation.
Turns project requirements in docs/REQUIREMENTS.md into a staged docs/PLAN.md with verification, handoff criteria, milestones, and dependencies. Use when PLAN.md is weak, missing, or stale.
Share bugs, ideas, or general feedback.
Step skill for the docs-orchestrator pipeline. Follows the step skill contract: parse args → dispatch agent → write output.
$1 — JIRA ticket ID (required)--base-path <path> — Base output path (e.g., .claude/docs/proj-123)<base-path>/requirements/requirements.md
<base-path>/planning/plan.md
Extract the ticket ID and --base-path from the args string.
Set the paths:
INPUT_FILE="${BASE_PATH}/requirements/requirements.md"
OUTPUT_DIR="${BASE_PATH}/planning"
OUTPUT_FILE="${OUTPUT_DIR}/plan.md"
mkdir -p "$OUTPUT_DIR"
Dispatch the docs-planner agent with the following prompt.
Agent tool parameters:
subagent_type: docs-plannerdescription: Create documentation plan for <TICKET>Prompt:
Create a comprehensive documentation plan based on the requirements analysis.
Read the requirements from:
<INPUT_FILE>The plan must include:
- Gap analysis (existing vs needed documentation)
- Module specifications (type, title, audience, content points, prerequisites, dependencies)
- Implementation order based on dependencies
- Assembly structure (how modules group together)
- Content sources from JIRA and PR/MR analysis
Save the complete plan to:
<OUTPUT_FILE>
After the agent completes, verify the output file exists at <OUTPUT_FILE>.
If no output file is found, report an error.