# Automation Opportunity Map

> Identify, evaluate, and prioritize enterprise workflows that can be automated with Codex Skills, scripts, tools, integrations, or operating-process changes. Use when Codex needs to analyze a process, find automation opportunities, estimate value, map inputs and outputs, or recommend a practical automation roadmap.

- Skill: `clarentcinematics/automation-opportunity-map` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add clarentcinematics/automation-opportunity-map`
- Raw SKILL.md: https://api.skillmd.com/api/skills/clarentcinematics/automation-opportunity-map/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: ClarentCinematics (https://skillmd.com/u/clarentcinematics)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/clarentcinematics/automation-opportunity-map

---


# Automation Opportunity Map

## Workflow

1. Map the workflow goal, trigger, actors, inputs, tools, decisions, outputs, and current pain points.
2. Identify repeatable steps, handoffs, data transformations, approval paths, and quality checks.
3. Classify opportunities as skill, script, integration, dashboard, template, or process redesign.
4. Score opportunities by value, frequency, complexity, risk, data sensitivity, and time-to-impact.
5. Recommend a staged automation roadmap with quick wins, dependencies, and validation criteria.

## Output Standard

Use this structure by default:

- **Workflow Summary**: current workflow, owner, frequency, and business outcome.
- **Pain Points**: friction, waste, rework, delay, or quality risk.
- **Automation Candidates**: opportunity, automation type, value, complexity, and risk.
- **Prioritization Matrix**: quick win, strategic bet, defer, or avoid.
- **Recommended Roadmap**: first experiment, next build, and longer-term system improvement.
- **Required Inputs**: data, artifacts, systems, permissions, and human review points.
- **Success Measures**: time saved, quality improved, risk reduced, or throughput gained.

## Rules

- Prefer narrow automations with clear ownership over broad vague transformation ideas.
- Flag privacy, compliance, access, and human-review requirements explicitly.
- Do not recommend full automation when human judgment is essential or source data is unreliable.
- Optimize for measurable operating leverage, not novelty.

## References

Read `references/opportunity-patterns.md` when the user asks for an intake form, prioritization rubric, or roadmap format.