publish-step7

Generate delivery inventory and _meta.md distribution metadata for a PUBLISH_V version.

Updated May 20, 2026
One-click install
npx skills add https://github.com/kuro0107/madamisu-skills --skill publish-step7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-step7
Source: https://github.com/kuro0107/madamisu-skills/tree/main/plugins/madamisu/skills/publish-step7
Command: npx skills add https://github.com/kuro0107/madamisu-skills --skill publish-step7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It generates and presents a final delivery metadata file and confirmation step for the “publish” workflow, so the produced GM materials, handouts, evidence, and endings are packaged consistently.

Core Features & Use Cases

  • Delivery inventory generation: Scans the final folder (publish/v{PUBLISH_V}/) to count and list deliverables per filename pattern.
  • _meta.md creation in a fixed schema: Writes a distribution guide including what each file is for, who receives it, and when to share it.
  • User final approval gate: Shows a summary prompt and branches into either finishing (“y”) or collecting correction feedback (“n”) routed to the relevant prior phase.

Quick Start

Run publish-step7 for a known version to generate publish/v{PUBLISH_V}/_meta.md and confirm the final delivery contents for approval.

Frequently Asked Questions about publish-step7

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

FAQPage Schema
How do I generate a delivery checklist for game materials before final handoff?

To generate a delivery checklist for game materials, the Skill scans the publish folder to list deliverables and writes a distribution metadata file. It inventories markdown artifacts like GM notes, evidence, and character handouts for final approval.

What is a publish delivery metadata file and when do I need one?

A publish delivery metadata file is a distribution guide documenting what each file is for, who receives it, and when to share it. It is needed during the final approval stage to ensure consistent packaging of game materials.

How do I finalize markdown artifacts for a game publish workflow?

You finalize markdown artifacts by running the Skill on a selected publish version, which generates the _meta.md file and presents an interactive y/n approval gate to either finish the workflow or route correction feedback.

Can I add difficulty and play time information to a generated distribution guide?

Yes, the generated distribution guide uses placeholders for difficulty, play time, input directory, and repair count. These values are incorporated into the _meta.md file during the metadata generation process.

What happens if I do not approve the final delivery contents during the workflow gate?

If you do not approve the final delivery contents by selecting no, the workflow branches into collecting correction feedback. This feedback is then routed back to the relevant prior phase for adjustments.

Does the delivery checklist generation require any external dependencies or components?

No external dependencies or components are required. The generation relies on a filesystem-based listing of markdown artifacts within the publish directory to produce the final inventory and metadata.