Create a structured Game Design Document from briefs and research.
npx skills add https://github.com/MazenMrad/Obsidio --skill gds-create-gdd
Please help me install this Agent Skill. Skill: gds-create-gdd Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-create-gdd Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-create-gdd
GDS creation often suffers from scattered notes, inconsistent structure, and unclear project scope. This skill provides a guided, collaborative workflow to turn briefs, research, and brainstorming into a structured Game Design Document.
Use Case Examples:
Initiate the GDD workflow by loading existing briefs and proceeding to Step 2.
High-intent search queries and answers about installing and using this skill.
Creating a structured game design document from scattered notes is achieved by aggregating briefs, research, and brainstorming into a guided workflow. The process seeds an executive summary and builds out type-specific sections like core gameplay and progression.
Structuring a game design document for a specific game type involves classifying the game using a provided CSV, loading the corresponding guide, and validating concepts step-by-step. This generates tailored sections for mechanics, epics, and metrics.
Yes, you can use a guided GDD workflow to add features to an existing game project. The process handles brownfield projects by anchoring new concepts into the existing document structure through a step-by-step progression.
Step-by-step elicitation for planning game mechanics requires explicit user input to advance through each stage. It uses collaboration menus to refine concepts and validates decisions against a loaded game-type guide.
You do not need prior documentation to start game design document creation, as the workflow supports greenfield projects from a vague concept. It uses smart input discovery to aggregate any available briefs or brainstorming materials to seed the GDD.
A limitation of frontmatter-driven game design planning is that it requires explicit user input to advance through each of the 14 steps, preventing fully automated generation. Progress and decisions are strictly tracked within the structured frontmatter.
mblodeAggregate research sources into an executive briefing with thematic analysis.
DriveConnect-alphaCreate a structured Game Design Document covering core loop, mechanics, progression, and balancing.
MazenMradGenerate a game brief through an 8-step workflow with A/P/C menus.
joekhosbayarTranslate game concepts into a complete Game Design Document with gdd.md and epics.md.
