skills / business

create-prd

what it does

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Turn these kickoff notes into a PRD.”

Source material given with the request

Kickoff, Oct 14. Dana (PM), Luis (eng lead), Mei (design). - Groomers lose money on no-shows. No-show rate across our 340 grooming salons averaged 18% in Q3. - Idea: SMS and push reminders 48 hours and 3 hours before the appointment, with one-tap confirm or cancel. Cancelled slots get offered to a waitlist. - Luis: deposits would need a payment integration, about 2 extra months. Decided: no deposits in v1. - Decided: iOS and web first. Android later (only 9% of salon clients use Android). - Goal: bring no-shows from 18% to 12% within 3 months of launch. - Mei worried clients will get too many texts. Agreed: max 2 reminders per booking. - Unknown: whether salons will pay extra for SMS (costs us about $0.01 per text).
with the skill
# PRD: Appointment Reminders and Waitlist Backfill **Filename:** `PRD-appointment-reminders.md` **Source:** Oct 14 kickoff notes ## 1. Summary Reduce grooming appointment no-shows through SMS and push reminders with one-tap confirmation or cancellation. Offer cancelled slots to a waitlist so salons have a chance to recover lost bookings. Launch on iOS and web first, with no deposits. The goal is to reduce no-shows from 18% to 12% within three months of launch. ## 2. Contacts | Name | Role | |---|---| | Dana | Product manager | | Luis | Engineering lead | | Mei | Designer | ## 3. Background Across our 340 grooming salons, the average no-show rate was 18% in Q3. Missed appointments cost salons money.
Show the rest (91 more lines)
The proposed approach gives clients timely reminders and an easy way to release appointments they cannot attend. A waitlist helps salons fill those openings. Kickoff decisions: - Limit reminders to two per booking to avoid overwhelming clients. - Prioritize iOS and web. Android accounts for only 9% of salon clients and will follow later. - Exclude deposits from v1. Luis estimates payment integration would add about two months. ## 4. Objective Help salons keep more appointment slots filled while making it easy for clients to manage their bookings. **Primary key result:** Reduce the no-show rate from the Q3 baseline of 18% to 12% or lower within three months of launch—a six-percentage-point reduction. **Supporting measures:** Track reminder delivery, confirmations, cancellations, and the share of cancelled slots filled through the waitlist. These help explain results; targets have not been agreed. **Measurement requirement:** Before launch, confirm the baseline calculation and use the same definition and salon population for the launch comparison. A cancellation alone is not recovered revenue; track backfilled appointments separately. ## 5. Market Segments ### A. Salon teams managing appointment capacity Teams that lose revenue when clients miss appointments and need a practical way to refill cancelled slots. **Constraints:** Benefit depends on timely cancellations and available waitlist demand. Willingness to pay for SMS is unknown. ### B. Clients managing grooming appointments Clients who need help remembering appointments or an easy way to cancel when plans change. **Constraints:** Reminders must be limited. iOS and web are the first supported product surfaces; Android app support is deferred. ## 6. Value Propositions ### A. Salon teams - **Who:** Teams responsible for keeping grooming schedules filled. - **Why:** They need clients to attend or release slots early enough to refill them. - **What before:** The current reminder and backfill workflow is unknown; the measured outcome is an 18% no-show rate. - **How:** Send scheduled reminders, capture client responses, and offer cancelled slots to a waitlist. - **What after:** Fewer missed appointments and more opportunities to recover cancelled bookings. - **Alternatives:** Manual calls or texts and existing scheduling tools are alternatives to validate. The proposed advantage is a connected reminder-to-backfill flow. **Value proposition:** Help salon teams turn forgotten appointments into attended visits or refill opportunities, with less manual follow-up. ### B. Clients - **Who:** Clients with upcoming grooming appointments. - **Why:** They need to remember bookings and communicate changes easily. - **What before:** Current reminder and cancellation methods have not been documented. - **How:** Provide timely reminders with one-tap confirm or cancel actions. - **What after:** Clients can act quickly without receiving excessive reminders. - **Alternatives:** Personal calendars or contacting the salon directly. This solution combines the reminder and response in one place. **Value proposition:** Make it easy to remember, confirm, or cancel a grooming appointment, with no more than two reminders per booking. ## 7. Solution ### 7.1 Key flow 1. A client has an upcoming appointment. 2. The client receives reminders 48 hours and 3 hours before it. 3. The client confirms or cancels with one tap. 4. A cancellation updates availability and triggers a waitlist offer. 5. A waitlisted client accepts the available slot. ### 7.2 First-version requirements - **Reminders:** Support SMS and push at the agreed times, with a maximum of two reminders per booking. Cross-channel counting needs a decision before build. - **Client actions:** Support one-tap confirmation and cancellation. Keep appointment status consistent across supported surfaces. - **Waitlist backfill:** Offer cancelled slots to waiting clients. Prevent multiple clients from booking the same opening. - **Scheduling accuracy:** Stop pending reminders when a booking is cancelled; update them when it is rescheduled. - **Measurement:** Record delivery outcomes, client responses, waitlist offers, accepted slots, and final attendance. ### 7.3 Technology and cost SMS costs approximately $0.01 per text. Two SMS reminders would cost approximately $0.02 per booking, excluding waitlist messages and any other fees. No payment integration is included. ### 7.4 Assumptions and open questions Resolve before implementation: - Does the two-reminder cap apply across SMS and push combined? Proposed assumption: yes. - Should confirmation suppress the remaining reminder? - How are late bookings, time zones, and SMS consent handled? - Does an existing waitlist support this flow? How are recipients selected, and when do offers expire? - Are waitlist offers counted separately from reminders? - Will salons pay extra for SMS, and who covers costs at launch? - Can Android clients use SMS and web response links despite deferred Android app support? ## 8. Release **V1:** iOS and web reminders, confirm/cancel actions, waitlist backfill, and outcome tracking. **Later:** Android app support. Revisit deposits and payment integration separately. **Not in v1:** Deposits or more than two reminders per booking. **Timing:** No delivery estimate was agreed. Engineering should size the release after messaging rules and waitlist dependencies are resolved. Evaluate the no-show target three months after launch. --- *Intentionally omitted: competitive research, detailed wireframes, and a dated delivery plan.*
without
# PRD: Appointment Reminders & Waitlist Backfill **Status:** Draft for review **Kickoff:** October 14 **Team:** Dana (PM), Luis (Engineering Lead), Mei (Design) ## 1. Problem Grooming salons lose revenue when clients miss appointments. Across our 340 grooming salons, the average no-show rate was **18% in Q3**. Clients need an easy way to confirm or cancel upcoming appointments. Salons need an opportunity to refill cancelled slots. ## 2. Goal & Success Metrics **Primary goal:** Reduce the no-show rate from **18% to 12% within three months of launch**—a 6-percentage-point reduction. | Metric | Purpose | |---|---| | No-show rate | Primary success metric | | Confirmation and cancellation rates | Understand client response to reminders |
Show the rest (75 more lines)
| Percentage of cancelled slots filled through the waitlist | Measure recovered appointment capacity | | SMS volume and cost per booking | Monitor operating costs | | Reminder opt-out rate | Monitor notification fatigue | **Measurement details to finalize:** Define the eligible appointment population, no-show classification, and reporting method so post-launch results are comparable with the Q3 baseline. ## 3. Users - **Salon clients:** Receive reminders and confirm or cancel appointments. - **Waitlisted clients:** Receive offers for newly available slots. - **Salon staff:** Benefit from clearer appointment status and refilled cancellations. ## 4. V1 Scope ### Appointment reminders - Support **SMS and push** reminders. - Schedule reminders **48 hours** and **3 hours** before an appointment. - Limit reminders to **a maximum of two per booking**. - Include one-tap actions to **confirm** or **cancel** the appointment. ### Cancellation and waitlist backfill - Update appointment status when a client cancels. - Offer cancelled slots to clients on a waitlist. ### Platforms - Launch on **iOS and web**. - Defer Android; it accounts for **9% of salon clients**. ## 5. Functional Requirements | ID | Requirement | Acceptance criteria | |---|---|---| | R1 | Schedule appointment reminders | Eligible bookings are scheduled for reminders at 48 hours and 3 hours before the appointment. Handling of bookings created inside those windows must be defined before implementation. | | R2 | Enforce the reminder cap | No booking generates more than two reminders. Channel-counting rules must be resolved before launch. | | R3 | Enable one-tap confirmation | A client can confirm from a reminder, and the appointment status reflects that confirmation. | | R4 | Enable one-tap cancellation | A client can cancel from a reminder, and the appointment status reflects that cancellation. | | R5 | Stop obsolete reminders | Cancelled appointments do not receive further appointment reminders. | | R6 | Offer cancelled slots to the waitlist | A cancellation makes the slot available for a waitlist offer. Offer ordering, expiration, and acceptance rules must be defined before implementation. | | R7 | Support launch platforms | Relevant client interactions work on iOS and web; Android-specific support is not required for v1. | *R5 is a proposed supporting requirement, not an explicit kickoff decision.* ## 6. Out of Scope - **Deposits and payment integration.** Explicitly excluded from v1; engineering estimates payment integration would add approximately two months. - **Android-specific support.** Deferred until after the initial release. ## 7. UX Principles - Make confirmation and cancellation clear and low-friction. - Minimize notification fatigue through the two-reminder cap. - Clearly communicate the outcome of a confirmation, cancellation, or waitlist acceptance. ## 8. Open Questions | Question | Why it matters | |---|---| | Will salons pay extra for SMS? | SMS costs approximately **$0.01 per text**; pricing and cost ownership remain undecided. | | How are SMS and push selected or combined? | Sending both at both scheduled times could conflict with the two-reminder cap. | | Does confirmation suppress the later reminder? | Affects notification fatigue and reminder behavior. | | What happens for late-created or rescheduled bookings? | Requires scheduling rules that preserve the reminder cap. | | How are waitlist clients prioritized, and how long do offers remain valid? | Needed to implement reliable backfill behavior. | | Do waitlist offers count toward the reminder cap? | The kickoff cap refers to reminders per booking; treatment of slot offers is unresolved. | | What consent, opt-out, and notification-permission handling is required? | Must be addressed for SMS and push delivery. | ## 9. Launch Readiness Before launch: - Resolve channel behavior, reminder-cap interpretation, and waitlist allocation rules. - Decide SMS pricing or approve absorbing the cost. - Validate reminder scheduling, appointment-state updates, and waitlist flows on iOS and web. - Instrument the success and guardrail metrics. - Finalize rollout scope and the three-month measurement plan. **Launch date:** Not set in the kickoff notes.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
bus-driver-assignment

“Write the PRD for a driver-assignment feature in our school bus software.”

dental-intake-lean

“Write a PRD for this. Keep it to a page or two so the clinic managers will actually read it.”

kickoff-notes-prd

“Turn these kickoff notes into a PRD.”

review-checkout-prd

“Can you review this PRD before I send it to engineering?”

vague-ai-prd

“Write a PRD for adding AI to our invoicing app.”

Install

Download the .zip and unzip it. Put its files, in a folder named create-prd, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.