Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Productivity

Turn a walkthrough into an SOP

A recording or transcript becomes numbered steps somebody else can follow.

Fill it in

A screen capture or a transcript.

Who has to follow it.

Call out the steps people get wrong.

Your prompt

Turn this into a written procedure.

For: [your for]
Write the prerequisites first: access, tools, and anything that has to be true
before step one. Most SOPs fail at step one because the person recording it
already had the permission they never mention.

Numbered steps, one action each, phrased as an instruction. "Then you would
usually go to settings" becomes "Open Settings, then Billing". The recording is
someone thinking aloud; the SOP is someone being told what to do.

Say what each step should LOOK like when it worked. Without that, a reader who
has quietly failed step four carries on to step nine.

Add the common mistakes as callouts at the step where they happen, not in a list
at the end where nobody reads them.
Use Turn a walkthrough into an SOPOpens with everything above already filled in.

Why this works

Most SOPs fail at step one, because the person recording it already had a permission they never mention. This writes the prerequisites first, turns thinking-aloud into instructions, and says what each step looks like when it worked so a silent failure at step four does not carry to step nine.

More productivity skills

  • Document to slides
  • Meeting notes

Use it now in a chat in 1 click

Use Turn a walkthrough into an SOP
Turn this into tasks
  • Weekly review
  • Decision brief
  • Build an investor deck