plan-documentation-roadmap — Claude Code command: how to install
plan-documentation-roadmap turns signals from analytics, tickets and stakeholder asks into a quarterly documentation roadmap with priorities, staffing and KPIs.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-documentation-roadmap.mdWhat plan-documentation-roadmap does
This command runs documentation planning end to end, from signal gathering to a plan you can defend. It starts with an audit: analytics, support tickets, recurring themes from NPS, requests from stakeholders. Candidate work then gets scored on impact, urgency and how well it matches the team you actually have.
Next comes the roadmap draft with initiatives, milestones, dependencies and owners. A governance layer sits on top: review cadence, localization, compliance steps. Output is a roadmap doc or deck, a resourcing and tooling plan, and a KPI tracker with targets and a reporting schedule.
Give it the period in --quarter, then audiences and formats as comma-separated lists (developers,admins, docs,video). --capacity and --tooling are optional. The documentation-architect and release-documentation-manager subagents carry the audit and launch-dependency work, while doc-requirements-matrix and versioning-dashboard skills feed in scoring and version support, so a project missing them leaves those steps without an executor.
What it helps with
- draft a quarterly documentation roadmap with owners and dates
- score candidate work by impact and urgency
- check whether the plan fits the team you have
- pull KPIs and risks into one pack for sign-off
- set review cadence and localization steps
Example prompts for the agent
- Plan docs work for the second quarter:
/technical-writing:plan-documentation-roadmap --quarter Q2 --audiences developers,admins --formats docs,video --capacity 2-writers - I need a half-year roadmap for admins and internal teams:
/technical-writing:plan-documentation-roadmap --quarter H1 --audiences admins,internal --formats docs,release-notes - Rework the plan for sales and support:
/technical-writing:plan-documentation-roadmap --quarter Q1 --audiences sales,cs --formats docs,tutorials
How to install plan-documentation-roadmap
Manually: put the files in place
.claude/commands/plan-documentation-roadmap.mdCall it with /plan-documentation-roadmap. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-documentation-roadmap.mdCall it with /prompts:plan-documentation-roadmap. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-documentation-roadmap.prompt.mdManually: put the files in place
.gemini/commands/plan-documentation-roadmap.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-documentation-roadmap
How do I install plan-documentation-roadmap in Claude Code?
Put the command file at .claude/commands/plan-documentation-roadmap.md inside your project. The invocation shown in the command is /technical-writing:plan-documentation-roadmap.
What does plan-documentation-roadmap do?
It audits signals, scores initiatives and returns a quarterly documentation roadmap with milestones, owners, a staffing plan and a KPI tracker.
Which subagents and skills does it call?
documentation-architect and release-documentation-manager handle the audit and launch dependencies, plus the doc-requirements-matrix and versioning-dashboard skills for scoring and version support.
Source text
plan-documentation-roadmap.md · Apache-2.0
--- name: plan-documentation-roadmap description: Produces quarterly documentation roadmap with priorities, staffing, and KPIs. usage: /technical-writing:plan-documentation-roadmap --quarter Q2 --audiences developers,admins --formats docs,video --capacity 2-writers --- # Command: plan-documentation-roadmap ## Inputs - **quarter** – planning period (e.g., Q1, Q2, H1, FY). - **audiences** – comma-separated list (developers, admins, operators, sales, cs, internal). - **formats** – docs, tutorials, video, release-notes, api-reference (comma-separated). - **capacity** – optional headcount or bandwidth context. - **tooling** – optional doc platform references. ## Workflow 1. **Audit & Signals** – pull analytics, support tickets, NPS themes, and stakeholder requests. 2. **Prioritization** – score opportunities by impact, urgency, and resource fit. 3. **Roadmap Draft** – map initiatives, milestones, dependencies, and staffing needs. 4. **Governance Layer** – define review cadences, localization, compliance steps. 5. **Executive Pack** – summarize KPIs, investments, and risks for approval. ## Outputs - Roadmap doc/deck with initiatives, timelines, and owners. - Resourcing + tooling plan with capacity notes. - KPI tracker outlining target metrics and reporting cadence. ## Agent/Skill Invocations - `documentation-architect` – leads audit + roadmap decisions. - `release-documentation-manager` – highlights launch dependencies. - `doc-requirements-matrix` skill – enforces requirement capture + scoring. - `versioning-dashboard` skill – ties roadmap to version support lifecycle. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents