feedback

Apply user feedback to madamisu scenario outputs via light or full updates.

Updated May 20, 2026

Search Tags:#versioning #feedback #editing #proofreading #scenario generation #regeneration #consistency checking

Ready to run

npx skills add https://github.com/kuro0107/madamisu-skills --skill feedback-kuro0107

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/kuro0107/madamisu-skills/tree/main/plugins/madamisu/skills/feedback
Command: npx skills add https://github.com/kuro0107/madamisu-skills --skill feedback-kuro0107

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns user feedback into concrete updates on previously generated scenario outputs, either by applying local edits or by creating a new heavier version to preserve consistency.

Core Features & Use Cases

Feedback-to-Update Pipeline: Analyzes feedback impact and then applies the appropriate modification flow to the selected output version.
Light vs Heavy Regeneration: Uses a lightweight in-place edit for local, low-impact changes, or a full regeneration for high-impact, cross-phase changes.
Consistency and Proofreading: Runs targeted consistency checks and performs proofreading to reduce typos, notation inconsistencies, and punctuation issues.
Version History Tracking: Updates output metadata and maintains a feedback history record for traceability.

Quick Start

Apply the feedback to the latest generated version by running: /madamisu:feedback "キャラAの動機をもっと深く"

Frequently Asked Questions about feedback

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

FAQPage Schema

How do I apply user feedback to generated scenario outputs while maintaining consistency?▼

To apply feedback to scenario outputs, the system reads existing version metadata, analyzes the feedback impact, and then performs either a lightweight in-place edit or a full regeneration to maintain internal consistency across worldbuilding, characters, and plots.

What is the difference between light and full regeneration when editing scenario files?▼

Light regeneration applies local in-place edits for low-impact changes, whereas full regeneration creates a new heavier version for high-impact, cross-phase modifications to ensure consistency across all affected scenario files.

How do I refine character motivations and plot details in a previously generated scenario version?▼

Refining character motivations and plots requires reading the target version metadata, optionally judging affected files via a dedicated agent, and then editing or regenerating the appropriate scenario files with logging and proofreading.

Does the feedback update process include consistency checking and proofreading?▼

Yes, the feedback update process runs targeted consistency checks and performs proofreading to reduce typos, notation inconsistencies, and punctuation issues while updating the scenario output metadata and feedback history.

How is version history tracked when applying feedback to scenario outputs?▼

Version history is tracked by updating output metadata and maintaining a feedback history record for traceability, ensuring all modifications to the scenario files are logged and accessible.

Can I use this feedback workflow for cross-phase changes in worldbuilding and timelines?▼

Yes, this feedback workflow supports cross-phase changes in worldbuilding, character details, plots, secrets, or timelines by initiating a full regeneration to preserve consistency across all affected scenario output files.