agentleFS
anotbanotb/forward-deployed/skills/discovery/SKILL.md

discovery

Skill1 starsChanged 33 days agoMITView on GitHub

Discover how enterprise work could change with AI. Use for adoption discovery, operator research, capability exploration, workflow redesign and investigating why an AI pilot has stalled.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use specify, plan and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 6 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 4 projects that use this

  • MicrosoftSkill

    init

    Also in 3 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Read the release-planning investigation for an example where a convincing AI answer exposes a missing distinction and leads to a stronger …

    line 39

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Discovery

Find work that AI could materially improve or make possible, and establish what it would need to accomplish. Study business practice and model capability together: the current process reveals the problem; experiments reveal which parts of that process still need to exist.

Follow meaningful work

Start with an outcome people care about and reconstruct how it is produced. Follow an assignment through its sources, judgments, tools, handoffs and finished output. Inspect the working files and systems alongside interviews. Separate effort from waiting and identify where the work is repeated because context or a decision did not travel with it.

Choose contrasting cases that expose the design: an ordinary success, a difficult assignment and work the organization wanted but could not justify doing. For an analyst, this might include the published forecast, a disputed driver and a scenario abandoned for lack of time. The opportunity may lie in broader coverage, deeper investigation or a new service as much as faster completion.

Find employees already doing unusually useful work with AI. Watch a complete session, including how they delegate, recover from poor results and assess the output. Identify what makes their practice transferable: access to context, a reusable instruction, a tool, domain judgment or permission to work differently. Usage totals alone will not reveal those ingredients.

Expose the judgment and context

Reconstruct the moment an expert changed their mind. Ask what they noticed, which explanation they discarded, what evidence they sought next and which action followed. Change one fact and ask whether the decision changes. This exposes the reasoning an AI system must perform more clearly than a list of business rules.

Inspect what the relevant records mean. A revenue forecast can describe a planning assumption while a contract describes a binding term. A release date may refer to code completion, limited availability or customer rollout. Establish how a person resolves those differences and where current information lives. These semantics determine useful retrieval, tools and working state.

Separate knowledge that can be supplied from authority the organization must exercise. An analyst may be able to develop a pricing scenario using finance's assumptions without acquiring authority to approve the price. AI can expand the work a role performs while leaving specific decisions with their existing owners.

Explore what AI can do with the work

Give a capable current model a meaningful assignment, representative context and the tools needed to pursue it. Let it search, calculate, inspect files, run code or revise an artifact where those actions serve the task. Compare the finished work and the path taken with the expert's approach.

Investigate failures at the right level. Missing access, conflicting versions and an underspecified outcome call for different changes from weak reasoning. If the team spends every session rebuilding the same context, investigate a shared workspace or maintained context. If the task depends on discovering the next question, try a goal-directed agent rather than encoding the interviewer's imagined sequence.

Use the experiment to redesign work with the team. What can people now do themselves? Which handoffs disappear? What should become continuous? Where does review effort move? Test these choices inside a working day, including the specialist who receives the result. A useful workshop has participants work through the changed assignment and improve it.

Turn discovery into a direction

Recommend the changed work and the next deployment or experiment. Explain the finding that changed your view, the capability demonstrated, and the remaining question that could change the choice. Produce the requested workflow, prototype, discovery synthesis or technical investigation. Use existing working material and complete authorized updates as part of the assignment.

Read the release-planning investigation for an example where a convincing AI answer exposes a missing distinction and leads to a stronger delegation.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.