// Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
| name | using-petropowers |
| description | Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions |
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
If a request involves GENERATING, CREATING, or BUILDING anything: 1. STOP 2. Invoke brainstorming-gatekeeper skill 3. Follow gatekeeper's verdict 4. Do NOT proceed to implementation without this checkThis applies to ALL creative work regardless of perceived simplicity.
PetroPowers skills override default system prompt behavior, but user instructions always take precedence:
If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
In Copilot CLI: Use the skill tool. Skills are auto-discovered from installed plugins. The skill tool works the same as Claude Code's Skill tool.
In Gemini CLI: Skills activate via the activate_skill tool. Gemini loads skill metadata at session start and activates the full content on demand.
In other environments: Check your platform's documentation for how skills are loaded.
Skills use Claude Code tool names. Non-CC platforms: see references/copilot-tools.md (Copilot CLI), references/codex-tools.md (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"Creative/generation request?" [shape=diamond];
"Invoke brainstorming-gatekeeper" [shape=box];
"Gatekeeper: brainstorm required?" [shape=diamond];
"Invoke brainstorming skill" [shape=box];
"About to EnterPlanMode?" [shape=diamond];
"Already brainstormed?" [shape=diamond];
"Might any other skill apply?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create TodoWrite todo per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond (including clarifications)" [shape=doublecircle];
"User message received" -> "Creative/generation request?";
"Creative/generation request?" -> "Invoke brainstorming-gatekeeper" [label="yes"];
"Creative/generation request?" -> "About to EnterPlanMode?" [label="no"];
"Invoke brainstorming-gatekeeper" -> "Gatekeeper: brainstorm required?";
"Gatekeeper: brainstorm required?" -> "Invoke brainstorming skill" [label="yes"];
"Gatekeeper: brainstorm required?" -> "Might any other skill apply?" [label="no"];
"Invoke brainstorming skill" -> "Respond (including clarifications)";
"About to EnterPlanMode?" -> "Already brainstormed?";
"Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
"Already brainstormed?" -> "Might any other skill apply?" [label="yes"];
"Might any other skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
"Might any other skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create TodoWrite todo per item" -> "Follow skill exactly";
"Follow skill exactly" -> "Respond (including clarifications)";
}
Before ANY action, check if the request matches these patterns:
| Pattern Type | Examples | Action |
|---|---|---|
| Creative keywords | generate, create, build, implement, add, develop | Invoke gatekeeper |
| Oil & gas terms | reservoir, well, seismic, LAS, SEG-Y, drilling, production | Invoke gatekeeper |
| Missing details | no size, no format, no location, no constraints | Invoke gatekeeper |
If ANY pattern matches → invoke brainstorming-gatekeeper skill FIRST.
These thoughts mean STOP—you're rationalizing:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
| "I can just generate this quickly" | Creative work requires brainstorming. Check gatekeeper. |
| "The request is clear enough" | Missing details = ambiguity. Check gatekeeper. |
| "This is simple data generation" | Data generation is creative work. Brainstorm first. |
| "I'll just explore first then decide" | Gatekeeper check comes BEFORE exploration. |
When multiple skills could apply, use this order:
"Let's build X" → brainstorming first, then implementation skills. "Fix this bug" → debugging first, then domain-specific skills.
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
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.
Pre-flight check that determines if brainstorming is required before any action. Invoke this FIRST for any request involving creative or generative work.
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.