skills.rest
afovea
afoveaCOMMUNITY
Explore all skills by this author →
GitHub

requirements-generator

Transform informal game development requests into detailed implementation briefs.

Updated May 18, 2026
Search Tags:#scoping#production#requirements#game-design#brief#task-intake
One-click install
npx skills add https://github.com/afovea/game-dev-skills --skill requirements-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-generator
Source: https://github.com/afovea/game-dev-skills/tree/main/plugins/game-team/skills/requirements-generator
Command: npx skills add https://github.com/afovea/game-dev-skills --skill requirements-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity gap between a raw feature request and a concrete implementation plan, preventing scope creep and ensuring technical feasibility.

Core Features & Use Cases

  • Structured Intake: Converts vague requests into a standardized format covering functional requirements, feel targets, and constraints.
  • Risk Mitigation: Automatically surfaces blocking questions, assumptions, and potential performance or platform implications.
  • Use Case: When a designer asks for a new stamina system, this skill generates a comprehensive brief including UI requirements, save-game implications, and edge cases for the engineering team to follow.

Quick Start

Invoke the requirements-generator skill with your rough feature request to receive a structured implementation brief.

Frequently Asked Questions about requirements-generator

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

FAQPage Schema
How do I turn a rough game design idea into a production-ready implementation brief?▼

Generate a structured task intake brief by inputting informal feature requests to receive standardized documentation covering functional requirements, feel targets, and development constraints for game design.

What is the best way to scope game development tasks and prevent scope creep?▼

Scoping game development tasks prevents scope creep by identifying explicit assumptions, functional requirements, and edge cases before engineering begins, ensuring technical feasibility and team alignment.

Can I use this to clarify vague feature requests for UI and gameplay systems?▼

Clarify vague feature requests for UI and gameplay systems by operating across gameplay, UI, and technical systems to identify functional requirements, edge cases, and platform implications.

How do I identify edge cases and blocking questions before engineering starts?▼

Identify edge cases and blocking questions before engineering starts by automatically surfacing explicit assumptions, performance implications, and platform constraints when generating an implementation brief.

Related Skills

Explore More Product & Management Skills→
Leep-GHLeep-GH

prd-intake

Translate non-technical PRDs into architecture decisions and a Build Plan.

Community
Intermediate
andebet07-ossandebet07-oss

figma-implement-design

Translate Figma designs into UI code using project design tokens.

Community
Advanced
rik-simformrik-simform

sdlc-traceability

Automate requirements traceability maintenance across SDLC tools.

Community
Intermediate
oAISAooAISAo

godot-architecture

Enforce data, logic, and UI separation in Godot projects with dedicated managers and signals.

Community
Intermediate