opportunity-design
Skill1 starsChanged 34 days agoMITView on GitHub
Develop enterprise AI opportunities and use cases that change how work gets done or create new services. Use to expand an automation request, discover work the organization could not previously afford, or turn a business ambition into a concrete first build.
In this repository15 other files it gives its agents.
- adoption-and-scaleSkill
- capability-explorationSkill
- context-designSkill
- discoverySkill
- enterprise-engagementSkill
- enterprise-integrationSkill
- evaluate-and-improveSkill
- executive-communicationSkill
- field-productizationSkill
- get-startedSkill
- meeting-synthesisSkill
- solution-designSkill
- technical-deliverySkill
- use-case-portfolioSkill
- value-caseSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Follow a concrete situation through to its outcome.
- Distinctive: line 16
Use these prompts where they open a worthwhile direction:
- Distinctive: line 36
Keep the ambition and the first deployment connected.
- Distinctive: line 42
Read enterprise opportunity examples when widening a narrow request or choosing between different experiences.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Opportunity design
Develop a point of view about what the enterprise could do with capable AI, then make the work tangible. Use its customers, expertise, systems, and ambitions as design material. A useful opportunity gives someone a new ability or materially improves an outcome.
Find the opportunity in the work
Follow a concrete situation through to its outcome. Look for work that waits for an expert, disappears between teams, repeats when circumstances change, or never gets attempted. Ask what people would investigate, create, personalize, or complete if assembling context and applying expertise became much cheaper.
Learn how the strongest practitioners work: what they notice, which explanations they test, how they use systems, and when they change course. Those moves are material for the proposed capability. Look at employee experiments too; a useful tool someone built for themselves can reveal a broader need.
Use these prompts where they open a worthwhile direction:
- Delegate a whole assignment. A procurement agent could interpret a location's opening plan, reconcile requirements with approved products, investigate substitutes, and prepare valid purchase requests. Follow the work across systems until it reaches a usable result.
- Extend expert reach. Give each account, location, or product the investigation currently reserved for a few. Find the additional decisions or services that wider coverage would support.
- Change the pace. Turn a quarterly investigation into continuing work that revisits explanations as evidence changes and prepares the next useful action.
- Make working artifacts. Let employees create a runnable analysis, simulator, prototype, or operational tool, then change assumptions and use it on their own work. This can expand what a role can accomplish.
- Create a service. Give customers direct access to a capability previously delivered through a costly engagement: implementation, analysis, personalized learning, or sustained operational support. Design the service and its delivery economics together.
Develop the direction that fits the situation. These are ways to generate ideas, not categories every proposal needs to fill.
Design the assignment
Describe what it must figure out: competing explanations, an unfamiliar system, a feasible plan, an applicable precedent, a missing requirement, or the next investigation. Name the tools and feedback that let it make progress. Choose the interface around the assignment: an existing queue, editable workspace, tool, or conversation.
Explore current capabilities when they change the idea. Try relevant products, models, integrations, and creation tools on the task. A successful probe can justify a different interface, longer assignment, broader population, or more delegation. Keep technology choices open until the needed behavior has been demonstrated.
Walk through one case from request or trigger to completion. Show what the employee delegates, what happens independently, what persists between sessions, what the system produces or changes, and where human judgment enters. Identify the business objects and systems involved so that the experience can become an implementation brief.
Choose the first build
Keep the ambition and the first deployment connected. Narrow the population, environment, or action scope while preserving the defining work. For a procurement agent, the first build should turn a changing requirement into an executable purchasing plan in the test system.
Build or run the smallest useful experience that exposes the difficult dependency. Test whether it finds a better option, completes the assignment, enables a new task, or produces something the recipient uses. Measure the resulting work and the effort required to finish it.
Recommend a direction and explain the alternative that matters. Deliver a scenario, prototype, concept brief, or developed opportunity record suited to the decision. Include the value mechanism, first commitment, and result that would justify expansion.
Read enterprise opportunity examples when widening a narrow request or choosing between different experiences.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

