publish-step3

Generate a review-ready game design summary and gate progression on user approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a game-design artifact set into a clear, human-readable summary and enforces an explicit approval gate before continuing the publish workflow.

Core Features & Use Cases

  • Design-summary formatting: Produces a structured recap of phase composition, difficulty reflection points, special rules, and ending branches for quick review.
  • Controlled user confirmation: Prompts the user with a single decision point to proceed, stop, or apply feedback.
  • Feedback-driven rework: Captures user feedback, then triggers the prior publish step (step2) with the feedback included to refine the design.

Quick Start

Run publish-step3 after step2 has generated the required publish/v{PUBLISH_V} files to display the design summary and request approval with [y/n/f].

Frequently Asked Questions about publish-step3

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

FAQPage Schema
How do I add an approval gate to a markdown game design workflow?

An approval gate for a markdown game design workflow requires a skill that reads design artifacts, formats a structured review summary, and prompts the user for explicit y/n/f confirmation before proceeding.

How does feedback branching work in a publish workflow?

Feedback branching in a publish workflow captures user feedback and triggers the prior step, such as publish-step2, with the feedback included to refine the design artifacts and re-enter the review cycle.

What is the best way to summarize game design outputs for user review?

Summarizing game design outputs for user review involves formatting phase composition, difficulty reflection points, special rules, and ending branches from markdown files into a deterministic, human-readable display.

Can I use this workflow orchestration step without prior markdown files?

You cannot use this workflow orchestration step without prior markdown files. It requires parsing a specific version variable and reading publish/v{PUBLISH_V}/02_game_design.md and 02_info_disclosure_matrix.md.