product-documentation

Consolidate PDLC artifacts into a navigable documentation hub.

Updated Nov 8, 2025

Search Tags:#documentation #audience #handover #PDLC #artifact inventory #documentation hub

Ready to run

npx skills add https://github.com/ivanyeors/product-agentic-templates --skill product-documentation-ivanyeors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-documentation
Source: https://github.com/ivanyeors/product-agentic-templates/tree/main/.cursor/skills/12-product-documentation
Command: npx skills add https://github.com/ivanyeors/product-agentic-templates --skill product-documentation-ivanyeors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered PDLC artifacts into a single, navigable documentation hub that serves stakeholders, end users, developers, designers, and ops.

Core Features & Use Cases

Produces a Product Documentation Hub containing user guides, technical docs, design system reference, operations manual, and decision log.
Serves as a ready-made documentation package for post-deployment handoffs, audits, and knowledge transfer across teams.
Use Case: When a product ships, run Phase 12 to assemble all phase outputs into a cohesive, audience-specific documentation package.

Quick Start

Create a comprehensive Documentation Hub after deployment by consolidating artifacts from all PDLC phases.

Frequently Asked Questions about product-documentation

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

FAQPage Schema

How do I consolidate scattered PDLC artifacts into a single documentation hub?▼

Consolidate scattered PDLC artifacts into a single documentation hub by assembling outputs across all phases into audience-specific documents. This creates a navigable package containing user guides, technical docs, and operations manuals as a single source of truth.

What is the best way to create audience-specific technical documentation for a product handover?▼

Create audience-specific technical documentation for handover by consolidating phase outputs into tailored guides. This process produces distinct documents for stakeholders, end users, developers, designers, and ops teams from a unified artifact inventory.

How do I ensure my documentation hub maintains a single source of truth across all product phases?▼

Maintain a single source of truth by ensuring each document in the hub states its specific audience, includes a Last Updated date, identifies an owner, and links directly back to the original scattered PDLC phase artifacts.

Can I generate a complete post-deployment documentation package including a decision log and design system references?▼

Generate a complete post-deployment documentation package by running the final PDLC phase to assemble all outputs. This produces a cohesive bundle including user guides, technical docs, design system references, operations manuals, and the decision log.

Does this documentation hub approach work for knowledge transfer across different teams like developers and ops?▼

This documentation hub approach works effectively for knowledge transfer across teams by producing audience-specific outputs. It generates tailored technical docs for developers and operations manuals for ops teams from the consolidated PDLC artifacts.

What do I need to assemble a comprehensive product documentation package after deployment?▼

To assemble a comprehensive product documentation package after deployment, you need the completed outputs and artifacts from all preceding PDLC phases. These scattered items are then consolidated into the navigable documentation hub.