promptstudio
promptstudio's Prompts
Product Requirements Document (PRD) Writer
Turn a product idea into a complete PRD: problem, users, scope, user stories, acceptance criteria, metrics, and launch risks.
Act as a senior product manager writing a PRD that engineering, design, and GTM can actually execute. Be precise about what is in, what is out, and what is still unknown. Do not dress guesses up as facts. Inputs: - Product / feature: [Name and one-line idea] - Problem: [Who hurts and how] - Users: [Primary and secondary] - Platform: [Web / iOS / Android / API / internal] - Business goal: [Revenue, retention, expansion, cost, compliance] - Constraints: [Time, stack, legal, dependencies] - Known unknowns: [List, or "none yet"] - Success metric I care about: [North-star or proxy] Generate: 1. Summary: 8-12 sentences. What we are building, for whom, why now, and what "done" means for v1. Flag any Input that is still vague. 2. Problem and context: Current workaround. Cost of the workaround. Why existing tools or the current product fail. Evidence: separate Provided (from Inputs) vs Assumed (label each assumption). 3. Goals and non-goals: - Goals (3-6): Outcome-based, testable. - Non-goals for v1: Explicit cuts. Include at least two tempting features we will refuse. 4. Users and JTBD: Primary user, secondary user, anti-user (who this is not for). For the primary user: job-to-be-done statement, trigger, desired outcome, current alternatives. 5. Scope: In-scope list. Out-of-scope list. Open questions with an owner suggestion (PM / Eng / Design / Legal / GTM). 6. User stories (8-12): Format "As a [user], I want [action], so that [outcome]." Tag each P0 / P1 / P2. P0 must be a shippable vertical slice, not a layer of polish. Include 1-2 negative stories (what the system must not do). 7. Acceptance criteria for every P0 story: Given / When / Then. Include empty, error, permission, and mobile/narrow-viewport cases where relevant. No "should feel fast" without a number or a qualitative test method. 8. UX notes: Happy path in 6-10 steps. Empty states. Edge cases. Key copy (buttons, errors). What must be designed vs. what can ship with existing patterns. 9. Analytics and success metrics: Leading and lagging metrics. Event names (object_action). Guardrail metrics that would make us roll back. How we will decide to iterate vs. kill after launch. 10. Launch plan: Feature flag / staged rollout sketch. Internal dogfood. Beta criteria. Support and docs needed. GTM one-pager bullets (who we tell, what we claim, what we will not claim). 11. Risks and unknowns: Table: risk | likelihood (Low/Med/High, labeled as judgment) | impact | mitigation | trigger to escalate. Include at least one dependency risk and one "we might be solving the wrong problem" risk. Constraints: - No fake certainty. If Inputs do not include a number, write "unknown, need [source]" instead of inventing a TAM or conversion rate. - Do not invent APIs, vendors, or legal positions. - Stories must be independently testable. No "and also make it beautiful." - Write for a staff engineer who will challenge scope. Short sentences. Named sections. No vision-deck fluff.
TikTok & Short-Form Video Script with Retention Hooks
Write a TikTok, Reels, or Shorts script with a 3-second hook, beat-by-beat visuals, on-screen text, and a comment CTA.
Act as a short-form video director and retention editor who has shipped 500+ TikTok, Reels, and Shorts scripts for creators in education, fitness, and B2B. Write a script built to hold watch time past the 3-second drop-off and earn a comment, not a vague "value video." Inputs: - Platform: [TikTok / Reels / Shorts] - Topic: [What the video is about] - Audience: [Who this is for, age or job if known] - Length: [15s / 30s / 45s / 60s] - Goal: [Follows / saves / comments / site clicks / product waitlist] - On-camera style: [Talking head / voiceover + B-roll / screen record / skit / split demo] - Proof I can show: [Metric, demo, screenshot, or "none"] - Banned phrases I never say: [List, or "none"] - Brand / product to mention: [Name and how hard to push, or "none"] Generate: 1. Concept (4 lines): Working title. One-sentence promise. Why this angle beats a generic tip dump on [Topic]. Retention bet: the specific moment that should spike replays. 2. Hook variants (3): For each, write 0.0-2.5s spoken line AND matching on-screen text (max 8 words). Mix: pattern interrupt, specific number or confession, open loop. Mark the recommended hook. Do not start any hook with "Hey guys," "So," or a self-introduction. 3. Timestamped beat sheet: Break the full [Length] into beats every 2-4 seconds. Table columns: time range | spoken VO or on-camera line | on-screen text | visual / shot | cut or motion note. First beat is the hook. Last beat is the CTA. Include at least one visual pattern interrupt (zoom, cut to proof, text punch, or demo). If Length is 15s, 5-7 beats. 30s: 8-12. 45s: 12-16. 60s: 16-22. 4. Caption: 1-3 lines. First line is a search-friendly restatement of the promise. One question that people will answer in comments. 4-8 niche hashtags. No #FYP, #Viral, or #ForYou. 5. Audio directions: Original voice vs trending sound. If a sound, describe the energy (do not invent a specific licensed track name). Pacing notes (where to pause, where to speed up). Any captions-must-be-on note for silent autoplay. 6. Pinned comment CTA: The exact comment to pin. It should give a leftover tip, a resource, or a binary question. This is the comment CTA, not "link in bio" unless Goal is site clicks. 7. Follow-up videos (2): Title + 1-line hook for the next two videos that continue this topic so the account compounds. Constraints: - Ban: "Hey guys," "Hey everyone," "What's up," long intros, "In this video," "Without further ado," fake urgency, and asking viewers to smash anything. - Spoken lines must be sayable out loud. No tongue twisters. No paragraph-length sentences. - On-screen text is not a transcript dump. It is punchy support, 8 words max per beat unless showing a list. - If Proof is "none," do not invent a case study. Use a mechanism, demo, or honest "here is the framework" angle. - Cuts every 2-4s. No 8-second static talking-head holds unless the line is a deliberate pause after a claim. - Tone: Sharp, specific, and native to [Platform]. Write like a creator, not a brand agency.
LinkedIn Thought Leadership Post & Carousel Generator
Write a high-engagement LinkedIn post or carousel from a rough idea. Includes hooks, a save-worthy framework, and comment-bait CTAs.
Act as a LinkedIn ghostwriter and B2B content strategist who has grown multiple founder and operator accounts past 50k followers. Turn my raw idea into a post that earns saves, comments, and profile visits. Inputs: - Topic / idea: [Idea] - Audience: [Job titles and seniority] - Goal: [Follows / leads / comments / hiring] - Format: [Single post / Carousel / Poll] - Proof I can cite: [Metric, anecdote, or case] - Voice: [Direct / Warm / Analytical] - Length: [Short 800-1,200 characters / Medium 1,200-2,000 / Long 2,000-3,000] Generate: 1. Positioning: One sentence on the unique angle vs. generic LinkedIn advice on this topic. 2. Hook options (5): First-line hooks under 140 characters. Mix: contrarian claim, specific number, confession, pattern interrupt, question. Mark the recommended one. 3. Full post: Write the complete post in the requested length. Short lines. White space. No hashtag dump in the body. One concrete story or example in the middle. End with a single comment prompt (not "agree?"). 4. Carousel outline (if requested): 8-10 slides. Slide 1 = hook. Slides 2-8 = one idea each. Slide 9 = recap. Slide 10 = CTA. Max 25 words per slide. 5. First comment: A comment I should post immediately (adds a resource, caveat, or question) to seed the thread. 6. Hashtags: 3-5 niche tags. No #Success or #Mindset. 7. Visual note: What image, screenshot, or carousel cover would lift CTR. Constraints: - Ban: "In today's fast-paced world", "game-changer", "I'm humbled", "Let's dive in", emoji spam, fake "unpopular opinion" that is popular. - Sound like a practitioner, not a coach selling a course. - Claims need a number, example, or "in my experience" qualifier. - Tone: Specific, earned, and useful. Write like a smart coworker, not a personal brand.