No public results yet
Document a repeatable operating procedure from expert notes
Turn a documented workflow into a practical SOP with prerequisites, ordered actions, checks, exceptions and explicit gaps for review.
Create task-focused software instructions with prerequisites, expected outcomes, and visible gaps instead of invented interface details.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
Audience and experience level. Default: A new volunteer using the workshop's booking tool for the first time
One task the guide should explain. Default: Create a workshop session and share its booking link
Confirmed steps, interface labels, permissions, and limitations. Default: Fictional product notes: Coordinators can create sessions. Select Sessions, then New session. Enter title, start time, and seat limit. Select Save draft. Review the details, then select Publish. The published session has a Copy booking link button. Timezone behavior and editing after publication are not documented.
Write a how-to guide that helps A new volunteer using the workshop's booking tool for the first time complete Create a workshop session and share its booking link.
Verified interface steps and constraints:
Fictional product notes: Coordinators can create sessions. Select Sessions, then New session. Enter title, start time, and seat limit. Select Save draft. Review the details, then select Publish. The published session has a Copy booking link button. Timezone behavior and editing after publication are not documented.
Start with the intended result and prerequisites stated in the notes. Number the actions in the order a reader performs them. Use exact button and menu labels, one main action per step, and an expected result after important transitions. Suggest screenshot placement only where it would resolve a likely ambiguity.
End with a short completion check and any supported troubleshooting notes. Put missing prerequisites, unclear labels, and unverified error recovery in a separate editor's questions list. Do not invent screens, settings, commands, links, or product behavior. If a step depends on unspecified permissions or software version, flag that dependency. Keep the guide focused on completing this task rather than reviewing the product.No public examples yet for version 1
No public results yet
Turn a documented workflow into a practical SOP with prerequisites, ordered actions, checks, exceptions and explicit gaps for review.
No public results yet
Draft a listener-friendly episode page with accurate chapters, attributed highlights, resources, and clear missing-information notes.
No public results yet
Turn owned writing samples into a reusable editorial guide that distinguishes stable voice choices from topic-specific details.
No public results yet
Explore distinct headline angles within a length limit while preserving the article's actual scope and evidence.
No public results yet
Turn an audience goal and factual notes into a speakable speech with a clear opening, useful pauses, and a concrete ending.
No public results yet
Write a neutral news brief with a clear lead and attribution, while keeping unverified claims outside the draft.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.