documentation-publishing

Publishes structured technical documentation and user manuals to Flyee or local storage after project cycles.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill documentation-publishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-publishing
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/documentation-publishing
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill documentation-publishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish structured technical documentation and user manuals to Flyee after project cycles, ensuring handover and test guides are created and all docs are published or stored locally as needed.

Core Features & Use Cases

  • Automated creation of HANDOVER and TEST-GUIDE documents for a scope.
  • Publication of technical docs to Flyee (flow docs, TDD, design-system references) and local storage when required.
  • Generation of user guides for operators, mapped from published flows.

Quick Start

Generate the handover and test-guide documents for the scope, then publish all artifacts to Flyee or local storage according to configuration.

Frequently Asked Questions about documentation-publishing

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

FAQPage Schema
How do I publish technical documentation and user manuals to Flyee after a project cycle?

Publish technical documentation to Flyee by orchestrating database discovery, artifact upserts, and flow mapping to generate end-to-end publication workflows. This Skill automates the creation of handover guides, test guides, and user manuals for operators.

Can I generate handover and test guides automatically for my project scope?

Yes, automated generation of handover and test guides is enforced for your project scope. This Skill ensures these critical documents are created, mapped from published flows, and made accessible before completing the documentation publication cycle.

Does documentation publishing to Flyee support local storage when needed?

Documentation publishing supports local storage as an alternative to Flyee. The workflow upserts artifacts and publishes flow docs, technical design documents, and design-system references to either Flyee or local storage according to your configuration.

What is the best way to map published flows into user guides for operators?

Map published flows into user guides by orchestrating the publication workflow that enforces generation of operator-facing manuals. This process ensures artifacts are traceable and accessible after discovering databases and upserting artifacts.

Do I need any external dependencies to publish flow docs and user guides?

No external dependencies are required to publish flow docs and user guides. The Skill operates independently to orchestrate discovery, artifact upserts, and flow mapping for publication to Flyee or local storage.

What limitations exist when publishing technical docs to Flyee vs local storage?

The Skill publishes technical docs to Flyee or local storage based on configuration, but enforces mandatory creation of handover and test guides regardless of destination. Traceability and accessibility of artifacts are maintained across both storage options.