skills.rest
SeoJaeWan
SeoJaeWanCOMMUNITY
Explore all skills by this author →
GitHub

brainstorm

Produce a structured request-lock to resolve ambiguous user goals before planning.

1|Updated Mar 6, 2026
Search Tags:#planning#brainstorming#requirements#governance#artifact#decision-making#review-wiki
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill brainstorm-seojaewan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/.codex/skills/brainstorm
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill brainstorm-seojaewan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex entry skill for request-lock brainstorming. Use when the user's goal, scope, public surface, acceptance, exclusions, or user-visible UI direction must be decomposed and fixed in the user's own language before planning.

Core Features & Use Cases

  • Provide a structured approach to identify and lock unclear decisions across product, UX, and engineering planning.
  • Integrate with review-wiki preflight to surface blocking ambiguities, contracts, and ownership boundaries before the plan is formed.
  • Align multiple stakeholders by surfacing decision criteria and acceptable tradeoffs in a shareable artifact set.

Quick Start

Lock ambiguity by translating the user's goal into a concrete request-lock and preflight questions before planning.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I lock ambiguity in product requirements before planning?▼

Lock ambiguity by translating unclear goals, tradeoffs, and scope into a structured request-lock artifact. This surfaces decision criteria, ownership boundaries, and exclusions before formal planning begins.

What is a request-lock artifact in engineering and UX planning?▼

A request-lock artifact is a structured output that fixes unclear decisions and public surface constraints in user language. It aligns stakeholders by documenting decision criteria and acceptable tradeoffs before planning.

How do I surface blocking ambiguities across product, UX, and engineering teams?▼

Surface blocking ambiguities by running a preflight review-wiki check that identifies missing policy decisions, contracts, and ownership boundaries. This produces linked artifacts for stakeholder alignment.

When should I use brainstorming to decompose unclear user requests?▼

Use brainstorming when goals are unclear, tradeoffs exist, or policy decisions are missing across engineering, UX, and product planning, and when a wiki-backed artifact set is available for reference.

Can I integrate request-lock planning with a review-wiki artifact set?▼

Yes, request-lock planning integrates with review-wiki preflight to surface blocking ambiguities and contracts. It outputs linked artifacts that reference the wiki-backed set for planning.

What are the limitations of using a structured request-lock for decision-making?▼

Request-lock planning requires a wiki-backed artifact set to function effectively. It is limited to surfacing decision criteria and exclusions, not executing the plan itself.

Related Skills

Explore More Product & Management Skills→
GanyuanRanGanyuanRan
968

writing-plans

Convert approved specs into executable plans with ownership and verification.

Community
Advanced
imonmiimonmi

bmad-correct-course

Analyze cross-artifact impact to produce a Sprint Change Proposal.

Community
Advanced
bellugabelluga

rule-laravel-shared-workflow-definition-model-decision

Enforce Laravel workflow governance using the central decision-model rule.

Official
Intermediate
gesmith0606gesmith0606

gsd-new-project

Initialize projects by generating structured planning artifacts and phased roadmaps.

Community
Advanced