plan-session

Orchestrate structured design sessions to gather context and validate assumptions.

7|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/borkweb/skills --skill plan-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-session
Source: https://github.com/borkweb/skills/tree/main/skills/gstack/plan-session
Command: npx skills add https://github.com/borkweb/skills --skill plan-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps product designers understand the problem space fully before proposing solutions, ensuring the end product meets user needs and adds value.

Core Features & Use Cases

  • Context Gathering: Systematically gather project context and user goals.
  • Product Diagnostic: Perform a detailed diagnostic to uncover user pain points and requirements.
  • Design Partner: Serve as a collaborator, providing guidance and insights during design sessions.

Quick Start

Run the 'plan-session' skill to start a product design session.

Frequently Asked Questions about plan-session

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

FAQPage Schema
How do I structure a product design session to fully understand the problem space?

Structure a product design session by systematically gathering project context, performing a detailed diagnostic to uncover user pain points, and validating assumptions through critical questioning to inform effective product features.

What is structured questioning in product design and when do I need it?

Structured questioning in product design is a diagnostic method to explore solutions and validate assumptions before proposing them. You need it when you must ensure the end product meets user needs and adds value.

How to diagnose user pain points and requirements for internal tools?

Diagnose user pain points for internal tools by running a structured design session that acts as a product diagnostic, systematically gathering user goals and project context to uncover specific requirements.

Can I use a design partner approach for validating product feature assumptions?

Yes, you can use a design partner approach to validate product feature assumptions by collaborating through a structured session that uses critical questioning to explore the problem space and test your hypotheses.

What's the best way to gather project context and user goals before designing features?

The best way to gather project context and user goals is through an orchestrated design session that systematically collects inputs and performs a comprehensive diagnostic to fully understand the problem space.

When should I not use a structured design session for problem diagnosis?

You should avoid a structured design session when the problem space is already fully understood and validated, as the process focuses on comprehensively diagnosing user needs and uncovering requirements before proposing solutions.