brief-writing

Conducts a structured interview to turn a raw game idea into a product brief.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/rombel00/game-processes --skill brief-writing-rombel00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brief-writing
Source: https://github.com/rombel00/game-processes/tree/main/plugins/product-definition/skills/brief-writing
Command: npx skills add https://github.com/rombel00/game-processes --skill brief-writing-rombel00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw game ideas arrive vague and misaligned across stakeholders. This Skill runs a structured clarification interview that turns a rough concept into a professional product brief with a Job Story, hard constraints, RICE priority, acceptance criteria, out-of-scope items, and risks, before any design or development begins. ## Core Features & Use Cases - Clarification Loop: Asks 2-4 focused questions per round, tracks section completeness with a weighted uncertainty score, and handles "I don't know" answers by offering options or logging open questions. - Depth-Adaptive Scoping: Adjusts the interview to the declared process depth (one-evening prototype, backbone only, or full project), so a small game gets a three-line brief instead of a heavyweight document. - Autonomous Pipeline Mode: Given only an idea artifact, reconstructs the brief with clearly marked [assumption] entries and returns a JSON envelope for the orchestrator. - Use Case: A solo developer describes a card roguelike concept; the Skill interviews them on genre, platform, player, and constraints, then writes a committed docs/product/BRIEF.md ready for the brief-review gate. ## Quick Start Ask the agent to interview you and write a product brief for your game idea, starting with how big the project should be.

Frequently Asked Questions about brief-writing

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

FAQPage Schema
How do I write a product brief for a game idea?▼

Run a structured interview that covers the task and Job Story, player value, audience, hard constraints, acceptance criteria, and out-of-scope items. The Skill asks 2-4 focused questions per round and assembles the answers into a committed brief document.

What is a Job Story and how is it used in a brief?▼

A Job Story follows the format "When [situation], I want [motivation], so that [expected outcome]". It captures player context and intent instead of an abstract user role, and anchors the brief's problem statement.

Can the brief skill work without a live conversation?▼

Yes. In pipeline mode it takes an idea artifact as input, fills gaps with reasonable market and common-sense assumptions marked as [assumption], and outputs a complete brief plus a JSON status envelope for the orchestrator.

Does the brief include technical architecture or framework choices?▼

No. The brief deliberately excludes implementation decisions such as engines, frameworks, databases, or APIs. It records only what, why, who, when, and where; technical decisions are deferred to later architecture steps.

When should I skip the full brief process?▼

For a one-evening prototype, choose the "brief and straight to code" depth. The Skill then asks only one short round of questions and produces a three-line brief, skipping RICE prioritization and the review gate.