// Pre-flight check that determines if brainstorming is required before any action. Invoke this FIRST for any request involving creative or generative work.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Generate realistic synthetic oil & gas data (LAS well logs, SEG-Y seismic, core photos, time-series) with proper physical constraints for testing, demos, and training.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Meta-skill that detects software tasks and routes them to appropriate petropowers skills.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Handle real-time SCADA data, WITSML/PRODML streams, and time-series analysis.
| name | brainstorming-gatekeeper |
| description | Pre-flight check that determines if brainstorming is required before any action. Invoke this FIRST for any request involving creative or generative work. |
Pre-flight check that analyzes user requests and determines if brainstorming is required before any action.
Invoke this skill when the user request contains ANY of:
This is a gatekeeper skill. Follow the decision logic exactly. Do not rationalize around it.
| Category | Triggers |
|---|---|
| Creative | generate, create, build, implement, add, develop, make, set up, write, design, construct, establish |
| Oil & Gas | reservoir, well, seismic, production, drilling, LAS, SEG-Y, WITSML, PRODML, pipeline, formation, porosity, permeability, logs, survey |
| Ambiguity | Missing: size, format, location, constraints, data type, time range, count, structure |
IF (has_creative_keyword AND has_domain_context)
OR (has_creative_keyword AND has_ambiguity)
OR (has_domain_context AND has_ambiguity)
THEN → brainstorming required
ELSE → proceed directly
Analyze the user's request against the triggers above. Then output ONE of:
## Gatekeeper Decision: Brainstorming Required
**Triggers detected:**
- Keyword: [list detected creative keywords]
- Domain: [list detected domain terms]
- Ambiguity: [list missing details]
**Action:** Invoke brainstorming skill before proceeding.
Do NOT execute any implementation actions.
Then immediately invoke the brainstorming skill.
## Gatekeeper Decision: Proceed
**Analysis:** [Brief explanation why this is not creative work]
**Action:** Continue with appropriate skill or direct response.
Then continue with the appropriate action.
These requests do NOT require brainstorming:
| Thought | Reality |
|---|---|
| "This is too simple to brainstorm" | Simple requests often hide complexity. Run the check. |
| "I already know what they want" | That's an assumption. Run the check. |
| "I'll save time by skipping this" | Brainstorming catches scope issues early. Run the check. |
| "The user said it's urgent" | Urgency doesn't change the need for clarity. Run the check. |
Request: "I work on ppr-1 reservoir and need to generate data for the reservoir"
Analysis:
Decision: Brainstorming Required
Request: "What does the GR curve in a well log represent?"
Analysis:
Decision: Proceed (informational query)
Request: "Read the LAS file in data/well-1.las and show the curves"
Analysis:
Decision: Proceed (analysis of existing data)