documentation

Create post-launch documentation and knowledge-transfer materials with defined owners and review cadence.

Updated Nov 8, 2025

Search Tags:#templates #documentation #handoff #docs #phases #knowledge-transfer

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides comprehensive post-launch documentation and knowledge transfer across user, technical, and operations docs, ensuring a smooth handoff after deployment.

Core Features & Use Cases

Documentation governance: define owners, last-reviewed dates, and ongoing maintenance for all phase artifacts.
Artifact generation: produce Phase 1–6 documentation and handoff artifacts (audit reports, ADRs, runbooks, onboarding guides) to enable knowledge transfer.
Handoff framework: provide templates and checklists to accelerate documentation creation and review.

Quick Start

Publish the initial documentation package to your chosen docs site and link it from the project README.

Frequently Asked Questions about documentation

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

FAQPage Schema

How do I create post-launch documentation for a smooth project handoff?▼

Post-launch documentation requires defined audience templates, an entry-point document, owner assignment, and a recurring review cadence to ensure a smooth handoff after deployment. This process generates user guides, technical docs, and operations manuals.

What is documentation governance and how does it maintain post-launch docs?▼

Documentation governance maintains post-launch docs by defining owners, tracking last-reviewed dates, and enforcing ongoing maintenance for all phase artifacts. This ensures knowledge transfer materials remain current and reliable for operations.

How do I generate handoff artifacts like runbooks and onboarding packages after deployment?▼

Generate handoff artifacts by applying templates and checklists to produce Phase 1–6 documentation, including audit reports, ADRs, runbooks, and onboarding guides, enabling comprehensive knowledge transfer after deployment.

What do I need to set up before creating technical docs and operations manuals?▼

Before creating technical docs and operations manuals, you need defined audience templates, an assigned owner for the documentation, and an established recurring review cadence to keep the knowledge transfer materials current.

What's the best way to keep knowledge transfer materials current after launch?▼

The best way to keep knowledge transfer materials current is establishing a recurring review cadence with assigned owners and tracking last-reviewed dates for all phase artifacts, ensuring ongoing maintenance of your post-launch documentation.