publish-step1

Collect publishing-phase requirements and write them to a versioned markdown file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures the necessary inputs for the first phase of madamisu publish (a guided requirements intake), producing a structured requirements specification for later generation steps.

Core Features & Use Cases

  • Guided requirements intake for publishing: Collects difficulty, expected play time, desired game structure, and writing style in a step-by-step flow.
  • Optional inheritance from _config.md: Reuses compatible values (difficulty, play time, GM presence) when an earlier configuration file exists.
  • Outputs a versioned requirements spec: Saves the collected decisions into publish/v{PUBLISH_V}/01_requirements.md for downstream phases to consume.

Quick Start

Run publish-step1 by providing an input directory path and (optionally) a version number using: /madamisu:publish-step1 <INPUT_DIR> --v 1.

Frequently Asked Questions about publish-step1

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

FAQPage Schema
How do I collect publishing requirements for a murder mystery game scenario?

You can capture publication requirements for a murder mystery scenario through a guided intake interview that records difficulty, play time, structure, and writing style into a versioned markdown file.

What is a guided requirements intake for game publishing?

A guided requirements intake for game publishing is a step-by-step interview flow that captures essential player-facing configurations like difficulty and play time before generating downstream game materials.

Can I reuse existing configuration values when defining game publication requirements?

Yes, you can reuse existing configuration values. The intake process optionally inherits compatible settings like difficulty, play time, and GM presence from an existing output/_config.md file.

How do I start the first phase of a versioned publication workflow?

To start the first phase of a versioned publication workflow, provide an input directory path and version number to generate the initial requirements markdown file in the publish/v{PUBLISH_V}/ directory.

What format does the requirements specification output use?

The requirements specification output uses a versioned markdown format, specifically written to publish/v{PUBLISH_V}/01_requirements.md, ensuring downstream phases can easily consume the finalized requirement set.

Do I need a prior scenario configuration before running the publish intake?

Yes, a prior scenario configuration is needed. This skill applies to publication workflow phase 1 to generate GM materials and player-facing documents after scenario configuration already exists.