story-designer

Design Pendulum of Despair gap systems from the canonical gap analysis.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/gcko/pendulum-of-despair --skill story-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-designer
Source: https://github.com/gcko/pendulum-of-despair/tree/main/.claude/skills/story-designer
Command: npx skills add https://github.com/gcko/pendulum-of-despair --skill story-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined workflow to identify, design, and close gaps in Pendulum of Despair's game design by loading the canonical gap analysis, proposing next gaps, and updating design documents through audits, plans, and implementations.

Core Features & Use Cases

  • Load and read the canonical gap analysis to identify the next high-priority gaps.
  • Brainstorm, design, and plan systems that align with SNES-era constraints and canonical docs.
  • Implement and verify changes across docs, update gap statuses, and prepare changes for commit.

Quick Start

Run /story-designer to view gaps, then select a gap like '/story-designer 1.2' to begin designing.

Frequently Asked Questions about story-designer

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

FAQPage Schema
How do I identify and fill game design gaps in my documentation?

Game design gaps are identified and filled by loading a canonical gap analysis, brainstorming systems under SNES-era constraints, and generating documented specifications. This process audits design plans and updates gap statuses for commit preparation.

What is the best way to brainstorm game systems while maintaining SNES-era constraints?

The best way to brainstorm systems under SNES-era constraints is to cross-reference existing canonical docs during design. This ensures consistency, applies adversarial audits to implementation plans, and satisfies a verification checklist.

Can I use this workflow to audit existing game design documents?

Yes, you can audit existing game design documents by loading the canonical gap analysis and cross-referencing current docs. The workflow audits both design and implementation plans to ensure consistency before updating gap statuses.

How do I track and update the status of resolved game design gaps?

You track and update resolved game design gaps by satisfying the verification checklist after implementation. The workflow then updates the canonical gap analysis document and prepares the changes for commit and PR.

Does this game design workflow require any specific dependencies or components?

No specific dependencies or components are required to run this game design workflow. It operates independently to load gap analyses, generate documented specifications, and prepare changes for commit.