content-strategy

Plan documentation strategies using the Diataxis framework with gap analysis and phased roadmaps.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hpsgd/turtlestack --skill content-strategy-hpsgd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-strategy
Source: https://github.com/hpsgd/turtlestack/tree/main/plugins/product/user-docs-writer/skills/content-strategy
Command: npx skills add https://github.com/hpsgd/turtlestack --skill content-strategy-hpsgd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation for products and features often lacks a cohesive strategy, leading to missed coverage, scattered content, and weak onboarding. This Skill helps teams inventory existing material, assess coverage across the Diataxis quadrants (Tutorial, How-to, Reference, Explanation), identify gaps, and plan a prioritized roadmap for documentation work.

Core Features & Use Cases

  • Inventory existing content by Diataxis quadrant to understand current coverage.
  • Create a quadrant coverage matrix and perform gap analysis (missing, stale, orphaned content).
  • Produce a prioritised content backlog and phased roadmaps for foundation, completeness, and depth.
  • Establish content standards, templates, ownership, and maintenance rituals to keep docs fresh.
  • Use cases include onboarding new users, auditing developer docs, and aligning docs with product strategy.

Quick Start

Identify a product domain, inventory existing docs, map content to Diataxis quadrants, and draft a prioritized 4-week backlog.

Frequently Asked Questions about content-strategy

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

FAQPage Schema
How do I plan a documentation strategy using the Diataxis framework?

A Diataxis documentation strategy categorizes content into Tutorial, How-to, Reference, and Explanation quadrants. This framework ensures balanced coverage by mapping existing content to these quadrants, identifying gaps, and planning structured onboarding material.

What is the best way to audit existing product documentation for missing or stale content?

To audit existing documentation, inventory your content by Diataxis quadrant and create a coverage matrix. This process identifies missing, stale, and orphaned material, enabling you to build a prioritized backlog for remediation.

How do I create a prioritized content backlog and roadmap for technical writing?

Build a prioritized content backlog and roadmap by analyzing quadrant coverage gaps, assigning specific owners and deadlines to missing items, and structuring phased milestones for foundation, completeness, and content depth.

Can I use this approach to improve developer onboarding documentation?

Yes, this approach improves developer onboarding documentation by ensuring tutorial and how-to content gaps are prioritized. Mapping onboarding flows to the Diataxis quadrants guarantees new users receive foundational guidance.

What writing standards and maintenance rituals are needed to keep documentation fresh?

Keeping documentation fresh requires defining content standards, templates, explicit ownership, and recurring maintenance rituals. These governance elements ensure content remains actionable, owned, and aligned with evolving product strategy.