export-manuals

Consolidate workspace sessions and touched sources into structured operator manuals.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-manuals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-manuals
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/exports/export-manuals
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-manuals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow consolidates workspace sessions and artifacts into coherent operator manuals, reducing onboarding time and support overhead.

Core Features & Use Cases

  • Consolidates session outputs (exec/quick) and DECISIONs with plan-docs (Solution, Final behavior, Validations) into docs/manuals.
  • Generates an INDEX.md or per-topic dossiers depending on mode (complement vs regenerate) and keeps read-only report flow.
  • Supports onboarding, support, and operations teams by providing a structured, enterprise-friendly documentation package.

Quick Start

Invoke the export-manuals workflow via /w:export-manuals to create or refresh docs/manuals from your sessions.

Frequently Asked Questions about export-manuals

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

FAQPage Schema
How do I generate operator manuals from workspace sessions?

To generate operator manuals from workspace sessions, consolidate the session outputs and touched sources to summarize decisions, plan-docs, and code into structured documentation. This workflow produces an index or per-topic dossier depending on the selected mode.

What is the best way to consolidate onboarding documentation from session artifacts?

Consolidating onboarding documentation from session artifacts involves summarizing DECISIONs and plan-docs such as Solution, Final behavior, and Validations alongside touched code. This produces a structured, enterprise-friendly documentation package that reduces support overhead.

How does exporting manuals from a session corpus work?

Exporting manuals from a session corpus works by processing workspace sessions and touched sources to extract key decisions and validations. It operates in either complement mode to generate an INDEX.md or regenerate mode to produce per-topic dossiers.

Can I use session outputs to create read-only documentation for support teams?

Yes, you can use session outputs to create read-only documentation for support teams. The workflow consolidates exec and quick session outputs with plan-docs to produce usable manuals tailored for onboarding, support, and operations.

What is the difference between complement and regenerate modes for session documentation?

In session documentation, complement mode generates an INDEX.md file, while regenerate mode produces per-topic dossiers. Both modes consolidate workspace sessions and artifacts into structured operator manuals while maintaining the read-only report flow.

Do I need existing plan-docs to automate operator manual generation?

Yes, automating operator manual generation requires existing plan-docs such as Solution, Final behavior, and Validations. The workflow summarizes these alongside DECISIONs and touched code from the session corpus to produce coherent, structured documentation.