product-roadmap-energy-og
Sub-skill of product-roadmap: Energy & O&G (+2).
Best use case
product-roadmap-energy-og is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of product-roadmap: Energy & O&G (+2).
Teams using product-roadmap-energy-og should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/energy-og/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How product-roadmap-energy-og Compares
| Feature / Agent | product-roadmap-energy-og | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of product-roadmap: Energy & O&G (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Energy & O&G (+2) ## Energy & O&G - O&G Knowledge System enhancement - BSEE data integration - Lower Tertiary analysis automation ## Marine Engineering - Marine analysis standardization - Engineering verification system ## Web & Applications - Full-stack templates (Rails 8 + React) - Component library sync
Related Skills
worldenergydata-source-readiness
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
web-scraper-energy
Web scraping workflows for energy data collection from BSEE and BOEM using Scrapy
production-forecaster
Forecast oil & gas well production using decline curve analysis. Use when estimating EUR, generating type curves, fitting Arps models (exponential, hyperbolic, harmonic), or running reserve calculations. Supports conventional and unconventional wells, P10/P50/P90 probabilistic outputs, and multi-field type curve comparison.
energy-data-visualizer
Interactive visualization for oil and gas production data analysis using Plotly dashboards
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
github-roadmap-anchor-reuse
Reuse and reopen existing roadmap/epic GitHub issues instead of fragmenting work across duplicate replacement epics; retarget children and link active issues for continuity.
domain-gap-to-issue-roadmap
Deep multi-repo ecosystem audit → domain gap matrix → structured GitHub issue roadmap with epics. Use when the user wants to assess capabilities across repos and create a backlog of work items covering code, data, and documentation gaps.
testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
roadmap-to-github-issue-wave
Turn a roadmap/readiness review into a de-duplicated GitHub epic + child issue set with verification and explicit scope boundaries.
roadmap-issue-reopen-retarget-balance
Reopen existing roadmap anchors, close replacement epics, retarget new child issues, and add sequencing/de-dup comments so GitHub roadmap work preserves continuity and execution quality.
roadmap-anchor-issue-governance
Reopen and reuse the original roadmap/umbrella issue as the governance anchor; create new issues only for genuinely missing scoped work, then retarget/link all execution issues back to the anchor.