Guides
How to export and publish a reviewed pack
Export only after review. The export should carry ownership, approval status, review timestamps, source evidence, review notes, and unresolved open questions where available.
You should know what gets exported and where the reviewed pack can go next.
Finalize the pack
Finalization creates a clean deliverable from current review statuses. Approved outputs become the usable final pack. Rejected outputs are excluded from usable SOPs, rules, workflows, and skill files.
Export formats
- Copy or download the final output as Markdown.
- Use the browser PDF flow from the final output view when a PDF handoff is needed.
- Keep the Markdown export if the pack will move into a help center, internal wiki, onboarding playbook, or support macro system.
Where to publish
- Internal support playbook.
- Help-center draft queue.
- Onboarding handoff checklist.
- Support macro library.
- KCS-style knowledge-base workflow.
- Agent skill-file review backlog, only when your team is actually preparing agent instructions.
After export
Answer the post-export debrief if possible. The product captures whether the pack would be used this week, which output was most useful, what was wrong or low-value, whether the buyer would pay to repeat the workflow, and who else should see it.