get-context

Clarify and validate product design briefs with a three-question preflight capture.

488|76|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/openai/role-specific-plugins --skill get-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-context
Source: https://github.com/openai/role-specific-plugins/tree/main/plugins/product-design/skills/get-context
Command: npx skills add https://github.com/openai/role-specific-plugins --skill get-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather only the context needed for the next design action. This skill resolves or confirms the design brief; it does not implement UI or create durable design artifacts.

Core Features & Use Cases

  • Preflight brief capture: Ask three guiding questions to clarify missing product, visual, or interaction context.
  • Playback mode: If the brief is already known, replay the briefing succinctly and name the next workflow.
  • Design guardrails: Prevent UI scaffolding or implementation until the brief is confirmed.
  • Context loading: Load and apply saved user-context when available to ground decisions.

Quick Start

Answer the three questions to confirm the design brief and proceed.

Frequently Asked Questions about get-context

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

FAQPage Schema
How do I clarify a design brief before starting UI work?

To clarify a design brief before UI work, this skill enforces a preflight process by asking three guiding questions to resolve missing product, visual, or interaction context, ensuring clear direction before prototyping begins.

What is the best way to validate product context for a redesign?

The best way to validate product context for a redesign is using playback mode, which succinctly replays the existing briefing and explicitly names the next workflow to confirm direction before proceeding.

Can I use this skill to generate UI scaffolding during ideation?

You cannot use this skill to generate UI scaffolding during ideation because it implements design guardrails that prevent implementation and UI creation until the design brief is fully confirmed.

How do preflight design questions help prevent scope creep?

Preflight design questions prevent scope creep by gathering only the context needed for the next design action, resolving the design brief upfront rather than implementing UI or creating durable design artifacts prematurely.

Does this skill apply saved user-context for design workflows?

Yes, the skill applies saved user-context for design workflows by loading available context to ground decisions, ensuring the three preflight questions build upon existing product information.