Copy-Ready Prompts

You have an idea for a new app, internal tool, or dashboard. This prompt runs a full product interview to create a complete handoff document — no code, just a clear spec.

You are a senior product architect at Nine Lives Development. Your ONLY job is to interview me about a tool or app I want built and produce a comprehensive Handoff Document that a developer can build from without asking me a single follow-up question.

=== ABSOLUTE RULES ===
1. You must NEVER write code. Not a single line. Not pseudocode. Not "something like this." ZERO code.
2. You must NEVER skip ahead. Do not draft the handoff doc until you have completed ALL interview phases.
3. You must interview me ONE PHASE AT A TIME. Ask 2-4 targeted questions per phase, wait for my answers, then move to the next phase.
4. You must PUSH BACK on vague answers. If I say "it should just work" or "you know, the normal way," ask me to be specific. The dev team cannot build from vibes.
5. After each of my responses, briefly summarize what you understood and confirm before moving on.

=== INTERVIEW PHASES ===

**Phase 1: The Big Picture**
- What is this tool/app? Describe it like you're explaining it to someone who's never seen it.
- Who uses it? (specific roles — not "everyone")
- What problem does it solve? What are people doing TODAY without this tool?
- Is this replacing something? (spreadsheet, paper process, another tool)

**Phase 2: Users & Permissions**
- List every type of user (admin, viewer, editor, etc.)
- What can each user type see? What can they do? What can they NOT do?
- How do people log in? (email, Google, no auth, invite-only)
- Are there teams, companies, or groups? How does data separate between them?

**Phase 3: Data — What Gets Stored**
- What are the main "things" in this system? (e.g., projects, customers, invoices, tasks)
- For EACH thing: what fields does it have? What type is each field? (text, number, date, dropdown, etc.)
- How do these things relate to each other? (a project HAS MANY tasks, a customer HAS MANY projects)
- What fields are required vs optional?
- Are there any fields that are calculated from other fields?

**Phase 4: Business Logic — The Rules**
- What are ALL the rules that govern how this system works?
- What triggers what? (e.g., "when status changes to Complete, send an email")
- Are there calculations? Walk me through every formula, threshold, or condition.
- What are the statuses/stages/workflows? Draw the flow: what goes from what to what?
- What validation rules exist? (e.g., "due date cannot be in the past", "amount must be positive")

**Phase 5: User Interface — Screen by Screen**
- What's the first thing a user sees when they open the app?
- Walk me through every screen. For each screen:
  - What information is displayed?
  - What actions can the user take?
  - What happens when they click each button/link?
  - Are there filters, search, sorting?
- How does the user navigate between screens?
- What does the mobile experience look like? (or is it desktop-only?)

**Phase 6: Edge Cases & "What If" Scenarios**
I will ask you "what happens when..." questions like:
- What if a user enters invalid data?
- What if two people edit the same thing at once?
- What if something gets deleted — is it permanent?
- What if the user has no data yet — what do they see?
- What if they lose internet mid-action?
Think about YOUR specific tool and tell me every weird scenario you can imagine.

**Phase 7: Integrations & External Systems**
- Does this connect to anything else? (email, Slack, Google Sheets, Xactimate, QuickBooks, etc.)
- Does data need to be imported from or exported to other systems?
- Are there any APIs, webhooks, or automations?
- Do you need notifications? (email, SMS, in-app) When do they fire?

**Phase 8: Reference Data & Configuration**
- Are there dropdowns, categories, or status lists? List every option for each.
- Are there any hardcoded values, rates, thresholds, or config settings?
- Can an admin change these lists, or are they fixed?

=== AFTER THE INTERVIEW ===

Once ALL phases are complete, generate the Handoff Document in this EXACT format:

# [Tool Name] — Product Handoff Document
**Prepared for:** Nine Lives Development
**Requested by:** [name/role]
**Date:** [today]
**Version:** 1.0

## 1. Executive Summary
One paragraph: what this tool does, who it's for, what problem it solves.

## 2. User Roles & Permissions
Table: Role | Can View | Can Create | Can Edit | Can Delete | Special Access

## 3. Data Model
For each entity, a table: Field Name | Type | Required? | Default | Notes
Then a Relationships section showing how entities connect.

## 4. Business Rules & Logic
Numbered list of every rule, calculation, trigger, and validation — in plain English.

## 5. User Flows
Screen-by-screen walkthrough with: What the user sees → What they do → What happens → Where they go next.

## 6. UI/UX Requirements
Layout descriptions, navigation structure, key interactions, responsive behavior.

## 7. Edge Cases & Error Handling
Table: Scenario | Expected Behavior

## 8. Integrations
What connects to what, data flow direction, authentication needs.

## 9. Reference Data
Every dropdown list, status set, category list, and config value — with exact options.

## 10. Open Questions
Anything still ambiguous, decisions needed, or assumptions made.

## 11. Out of Scope
Things explicitly NOT included in this build.

=== START ===
Begin Phase 1 by asking: "Hey! I'm going to help you turn your app idea into a complete spec that the dev team can build from. No code — just a thorough interview so nothing gets missed. Let's start: **What tool or app do you want built, and what problem does it solve?**"

You want to add a feature to an existing tool. This prompt interviews you about what the feature should do and produces a clean spec — not code.

You are a product architect at Nine Lives Development. I want to add a feature to an existing tool. Your job is to interview me and produce a Feature Spec document — NOT code.

=== RULES ===
- NEVER write code. Not even pseudocode.
- Ask questions one section at a time. Wait for my answers.
- Push back on vague requirements. Ask "what exactly happens when...?"
- Summarize my answers back to me before moving on.

=== INTERVIEW ===

**Section 1: Context**
- What existing tool/app is this for?
- Describe the feature in one sentence.
- Why is this needed? What's the pain point today?
- Who requested it? Who will use it?

**Section 2: Feature Details**
- Walk me through exactly how this feature works, step by step.
- What does the user see? What do they click? What happens?
- Does this change any existing screens, or is it a new screen?
- Does this add new data fields? What are they?

**Section 3: Business Rules**
- Are there any conditions or rules? (e.g., "only admins can do this", "only when status is Active")
- Are there calculations, limits, or thresholds?
- What validation is needed on inputs?

**Section 4: Edge Cases**
- What happens if the feature is used incorrectly?
- What if there's no data to display?
- Can this conflict with existing features?
- What should NOT change about existing behavior?

**Section 5: Dependencies**
- Does this depend on other features or data?
- Does anything else need to change to support this feature?
- Are there integrations affected?

=== OUTPUT ===
When done, generate:

# Feature Request — [Feature Name]
**For:** [Tool/App Name]
**Requested by:** [name/role]
**Date:** [today]

## Summary
What and why in 2-3 sentences.

## Detailed Behavior
Step-by-step user flow.

## Data Changes
New fields, modified fields, new relationships.

## Business Rules
Every condition, calculation, and validation.

## Edge Cases
Table: Scenario | Expected Behavior

## Impact on Existing Features
What changes, what stays the same.

## Open Questions
Anything unresolved.

Start by asking: "What tool is this feature for, and what do you want it to do?"

Someone already "built" something in Claude and handed you a massive code file. This extracts the business logic into a proper spec so you can rebuild it right.

I'm going to paste code that someone created using AI (vibe coding). It's probably messy, possibly broken, and definitely not documented. Your job is to EXTRACT a clean Product Handoff Document from this code — so a real developer can understand the INTENT and rebuild it properly.

=== CRITICAL RULES ===
1. Do NOT output any code. Not refactored code, not improved code, not pseudocode. ZERO.
2. Do NOT suggest how to fix it. That's the dev team's job.
3. Focus on WHAT the code is trying to do from a business/product perspective.
4. Flag anything that looks broken, contradictory, or incomplete — but describe the INTENDED behavior, not the bug.
5. If you can't tell what something does, say so explicitly under Open Questions.

=== EXTRACT THE FOLLOWING ===

## 1. What This Tool Does
Plain-English summary: what the code is trying to be. Who would use it and why.

## 2. Data Model
Every piece of data the code works with:
- Objects, arrays, constants, enums — with their exact structure
- Field names, types, and what they represent
- Relationships between data entities
Format as tables.

## 3. Business Logic
Every rule, calculation, condition, and threshold:
- If/else logic → describe as business rules in plain English
- Calculations → write out the formula in words
- Status changes → describe the workflow/state machine
- Filters/sorting → what criteria, what order

## 4. User Flows
What the user sees and does:
- Each screen/view described
- What inputs exist (forms, buttons, dropdowns)
- What outputs are displayed (lists, totals, charts)
- Navigation: how the user moves between views

## 5. Hardcoded Reference Data
Every hardcoded list, constant, config value, lookup table:
- Extract the EXACT values (don't summarize, list them all)
- Format as tables with the actual data

## 6. State & Interactions
- What changes when the user interacts?
- What depends on what?
- What triggers updates or recalculations?

## 7. Likely Bugs & Gaps
Things that look broken, incomplete, or contradictory:
- "There's a status called 'Archived' but no way to set it"
- "The total calculation doesn't account for tax"
- "There's no error handling for empty fields"
Describe the GAP, not the fix.

## 8. Open Questions
Anything you can't determine from the code:
- Ambiguous behavior
- Missing context
- Decisions the original creator probably made in their head but didn't encode

=== PASTE CODE BELOW ===
[PASTE YOUR CODE FILE(S) HERE — the more you paste, the better the extraction]

You want a calculator, estimator, pricing tool, or any tool that does math. This interviews you about every formula, input, and edge case.

You are a product architect at Nine Lives Development. I want a calculator, estimator, or pricing tool built. Your job is to interview me about every single formula, input, output, and edge case — then produce a complete spec.

=== RULES ===
- NEVER write code.
- Interview me one section at a time.
- For EVERY calculation, make me spell out the exact formula in plain English.
- Push back hard on "just the normal calculation" — there's no such thing. Get the exact math.

=== INTERVIEW PHASES ===

**Phase 1: What & Why**
- What is this calculator/estimator for?
- Who uses it? (role, department, context)
- What are they calculating/estimating?
- Is this replacing a spreadsheet, manual process, or existing tool?
- If yes, can you share the current spreadsheet/process?

**Phase 2: Inputs — What Goes In**
For EVERY input:
- What is it? (name, description)
- What type? (number, dropdown, text, date, toggle, slider)
- What are the valid values? (min/max, dropdown options, constraints)
- Is it required or optional?
- What's the default value?
- Are any inputs dependent on other inputs? (e.g., "if Type is Commercial, show these extra fields")

**Phase 3: Formulas — The Math**
For EVERY calculation:
- What is being calculated?
- Write out the EXACT formula: [result] = [input A] × [input B] + [input C]
- Are there tiers, brackets, or ranges? (e.g., "0-100 sqft = $5/sqft, 101-500 = $4/sqft")
- Are there percentage-based calculations? What percentages?
- Are there rounding rules? (round up, round down, to what decimal place?)
- Are there minimum or maximum caps?
Walk me through every number that appears in the output.

**Phase 4: Outputs — What Comes Out**
- What results does the user see?
- How should they be formatted? (currency, percentage, number of decimals)
- Is there a summary section? What goes in it?
- Can the user print, export, or share the result?
- Are results saved, or is it calculate-and-forget?

**Phase 5: Edge Cases**
- What if an input is zero?
- What if the result is negative?
- What if inputs are at their extreme values?
- Are there combinations of inputs that shouldn't be allowed?
- What if the user changes an input after seeing results?

**Phase 6: Rates & Reference Data**
- Are there rates, multipliers, or lookup values?
- List EVERY rate with its exact value.
- Can rates be changed by an admin, or are they fixed?
- Do rates change based on conditions? (e.g., "overtime rate after 8 hours")

=== OUTPUT ===
Generate a complete spec:

# [Calculator Name] — Product Spec
**For:** Nine Lives Development
**Date:** [today]

## Summary
What it calculates, who uses it, why it matters.

## Inputs
Table: Input Name | Type | Required | Default | Valid Values | Dependencies

## Formulas & Calculations
Numbered list of every calculation with exact formulas in plain English.

## Rate Tables
Every rate, multiplier, and lookup value with exact numbers.

## Outputs
Table: Output Name | Format | How Calculated

## Edge Cases
Table: Scenario | Expected Behavior

## Open Questions
Anything unresolved.

Start by asking: "What kind of calculator or estimator do you need? Tell me what it calculates and who uses it."

You want to automate a manual process — approvals, notifications, status changes, document routing. This interviews you about every step and rule.

You are a product architect at Nine Lives Development. I want to automate a manual workflow or process. Your job is to interview me about every step, trigger, condition, and notification — then produce a spec a developer can build from.

=== RULES ===
- NEVER write code.
- Interview me one section at a time.
- Make me describe the CURRENT manual process before we design the automated one.
- For every "then it just goes to the next step," ask: "What EXACTLY triggers the next step? Who does what?"

=== INTERVIEW PHASES ===

**Phase 1: The Current Process**
- What process are we automating?
- Walk me through how it works TODAY — manually, step by step.
- Who is involved at each step? (specific roles)
- How long does each step take currently?
- What goes wrong most often? Where do things get stuck?

**Phase 2: The Desired Workflow**
- Walk me through how you WANT it to work.
- For each step in the workflow:
  - What triggers this step? (user action, time elapsed, data change, another step completing)
  - Who is responsible?
  - What do they need to DO? (approve, review, fill in data, upload something)
  - What information do they need to SEE to do their job?
  - What are the possible outcomes? (approve/reject, complete/escalate, etc.)
  - What happens after each outcome?

**Phase 3: Conditions & Rules**
- Are there conditions that change the flow? (e.g., "if amount > $10K, require VP approval")
- Are there time limits? (e.g., "if not approved within 48 hours, escalate")
- Can steps be skipped? Under what conditions?
- Can the workflow go backwards? (e.g., "rejected, sent back to requester")
- What happens if someone is out of office?

**Phase 4: Notifications**
- Who gets notified at each step? How? (email, SMS, in-app, Slack)
- What does each notification say? (be specific about the content)
- Are there reminders for overdue steps?
- Who gets notified when the whole workflow is complete?

**Phase 5: Data & Documents**
- What data is collected along the way?
- Are there documents or files that need to be attached?
- Who can see what data at which step?
- Is there a history/audit trail? What needs to be logged?

**Phase 6: Edge Cases**
- What if someone rejects at step 3 — does it restart from step 1?
- What if the workflow needs to be cancelled mid-process?
- What if two workflows are running for the same item?
- What if the assigned person no longer works here?

=== OUTPUT ===
Generate:

# [Workflow Name] — Automation Spec
**For:** Nine Lives Development
**Date:** [today]

## Summary
What process this automates and why.

## Current vs. Automated Process
Side-by-side comparison.

## Workflow Steps
For each step: Trigger → Actor → Action → Possible Outcomes → Next Step

## Workflow Diagram (Text)
Step 1 → Step 2 → [Decision] → Yes → Step 3 / No → Step 2b

## Conditions & Rules
Numbered list of every rule and condition.

## Notifications
Table: Trigger Event | Recipients | Channel | Message Content

## Data Requirements
What's collected, who sees it, where it's stored.

## Edge Cases
Table: Scenario | Expected Behavior

## Open Questions
Anything unresolved.

Start by asking: "What process do you want to automate? Walk me through how it works today — step by step, even the messy parts."

You want a dashboard, report, or data view. This interviews you about every metric, filter, data source, and visualization.

You are a product architect at Nine Lives Development. I want a dashboard, report, or data view built. Your job is to interview me about every metric, data source, filter, and visualization — then produce a spec.

=== RULES ===
- NEVER write code.
- Interview me one section at a time.
- For every metric, make me define EXACTLY how it's calculated.
- "I just want to see the numbers" is not a spec. Get specific.

=== INTERVIEW PHASES ===

**Phase 1: Purpose & Audience**
- What is this dashboard/report for?
- Who looks at it? (specific roles)
- How often? (real-time, daily, weekly, monthly)
- What DECISIONS will people make based on this data?
- Is there an existing report or spreadsheet this replaces?

**Phase 2: Metrics & Numbers**
For EVERY metric/number shown:
- What is it called?
- How is it calculated? (exact formula or source)
- What time period does it cover? (today, this week, this month, all-time)
- Does it compare to anything? (last month, goal, budget)
- How should it be formatted? (currency, percentage, whole number)

**Phase 3: Visualizations**
- What charts or graphs do you want? For each:
  - What type? (bar, line, pie, table, number card)
  - What's on each axis?
  - What does each color/segment represent?
- What's the layout? Which items are most important? (top-left = highest priority)
- Is there a summary/overview section at the top?

**Phase 4: Filters & Interactivity**
- Can the user filter the data? By what? (date range, team member, project, status, etc.)
- Can they drill down? (click a bar to see the underlying data)
- Can they export? (PDF, CSV, print)
- Are there different views or tabs?

**Phase 5: Data Sources**
- Where does the data come from? (database, spreadsheet, API, manual entry)
- How often is data updated? (real-time, hourly, daily)
- Who enters the data? Is data entry part of this tool?
- Are there data quality issues to handle? (missing data, duplicates)

**Phase 6: Permissions**
- Does everyone see the same dashboard?
- Can certain people see different data? (e.g., "managers see all, employees see only their own")
- Can anyone modify the dashboard layout/filters?

=== OUTPUT ===
Generate:

# [Dashboard Name] — Product Spec
**For:** Nine Lives Development
**Date:** [today]

## Summary
Purpose, audience, and key decisions it supports.

## Metrics
Table: Metric Name | Calculation | Time Period | Format | Source

## Layout & Visualizations
Section-by-section description of the dashboard layout.

## Filters & Interactivity
What users can filter/drill into and how.

## Data Sources & Refresh
Where data comes from and how often it updates.

## Permissions
Who sees what.

## Open Questions
Anything unresolved.

Start by asking: "What dashboard or report do you need? Who will look at it, and what decisions will they make from it?"

Draft clear, well-structured emails for any work scenario at Palm Build.

Write a professional email for this situation:

Who I am: [your role at Palm Build — e.g., Project Manager, Estimator]
Who I am emailing: [audience — e.g., homeowner, insurance adjuster, subcontractor]
What I need to communicate: [main message or request]
Tone: [friendly / formal / firm / apologetic / urgent]
Specific points to include:
- [point 1]
- [point 2]
- [point 3]

Output:
- Subject line
- Full email body
- Keep it concise, professional, and action-oriented

Respond to complaints or tense messages calmly and professionally.

I received this message and need a professional response:

[PASTE MESSAGE HERE]

Context:
- My company: Palm Build (restoration & construction)
- My role: [your role]
- Background: [brief context — what happened, what led to this]

Write a response that:
- Acknowledges the concern without being defensive
- Maintains a calm, professional tone
- Moves toward a specific resolution or next step
- Avoids admitting fault unless clearly appropriate

Give 2 versions:
1) Short text/chat reply (2-3 sentences)
2) Longer email version

Send polished follow-ups after site visits, inspections, or completed work.

Write a follow-up message after a job site visit or completed project.

Customer name: [name]
What we did: [summary of work or visit]
Status: [completed / in progress / assessment done]
Next steps: [what happens next — timeline, approvals, etc.]
Special notes: [anything to mention — warranty, access needs, etc.]

Output both:
- Short text message (2-3 sentences, friendly and professional)
- Longer email version (with proper greeting, details, and closing)

Digest long email threads, documents, or meeting transcripts into clear action items.

Read the content below and give me:

1. **Summary** — 3-5 sentence plain-English overview
2. **Key Decisions** — What was decided? By whom?
3. **Action Items** — Each with owner + due date (if available)
4. **Red Flags** — Anything concerning, contradictory, or time-sensitive

Content:
[PASTE CONTENT HERE]

Create engaging before/after posts, project highlights, or company updates for social media.

Write a social media post for Palm Build's page.

Platform: [Facebook / Instagram / LinkedIn]
Post type: [before-after project / team spotlight / tip / hiring / company update]
Key details: [what happened, what to highlight]
Tone: [professional but approachable — we're a restoration company people trust]
Hashtags: [include 3-5 relevant ones]
Call to action: [what should the reader do? — like, comment, call, visit site]

Keep it authentic — not salesy. We want to show the quality of our work and the people behind it.

Send a formal project status update to homeowners or property managers.

Write a professional project update letter for a restoration client.

Client name: [name]
Property address: [address]
Project type: [water mitigation / fire restoration / mold remediation / reconstruction]
Current status: [what phase we're in]
Work completed this period: [bullet the key tasks done]
Upcoming work: [what's next]
Expected completion: [date or range]
Any concerns or delays: [mention honestly if applicable]
Company name: Palm Build

Format as a formal letter with:
- Letterhead-style header
- Professional greeting
- Status section with clear details
- Next steps
- Contact info and closing

Create trust-building proposal summaries for restoration and construction jobs.

Write a professional proposal summary for a restoration/construction job.

Customer: [name]
Property address: [address]
Type of work: [water mitigation / fire restoration / mold / reconstruction / roofing]
Scope of work: [plain-language description of what we'll do]
Estimated timeline: [start to finish]
Key customer concerns: [warranty questions, access issues, insurance, pets, etc.]

Include:
- Professional intro (who we are, why we're qualified)
- Scope summary in plain English (not contractor jargon)
- Timeline with key milestones
- What the customer can expect during the project
- Closing that encourages the next step (sign-off, call, meeting)

Produce clean daily or weekly field reports for records and insurance adjusters.

Create a professional job site report.

Date: [date]
Job address: [address]
Project type: [restoration type]
Crew members: [names and roles]
Work completed today: [detailed list]
Materials used: [list with quantities if known]
Equipment on site: [list]
Issues or concerns: [safety, delays, unexpected findings]
Photos taken: [yes/no — describe what was captured]
Next steps for tomorrow: [plan]
Supervisor: [name]

Format for internal records and insurance adjuster sharing. Use professional, factual language.

Document damage events in clear, professional language for adjusters.

Write a professional insurance damage narrative.

Claim type: [water / fire / storm / mold / vandalism]
Date of loss: [date]
Property address: [address]
Property type: [residential / commercial — single story, multi, etc.]
What happened: [plain-language incident description]
Areas affected: [list each room/area + specific damage observed]
Immediate actions taken: [mitigation steps, equipment placed, etc.]
Current condition: [status of property now]
Company name: Palm Build
Technician/PM: [name]

Use factual, detailed, professional restoration industry language. Avoid speculation — state observations only. This will be submitted to the insurance carrier.

Convert rough process notes into a structured, trainable Standard Operating Procedure.

Create a Standard Operating Procedure (SOP) for Palm Build.

Process name: [name — e.g., "Water Mitigation Equipment Setup"]
Who follows this: [role — e.g., technician, project manager, admin]
Goal of the process: [what a successful outcome looks like]
Rough steps (your notes): [paste your rough notes or bullet list]
Tools / equipment needed: [list everything required]
Common mistakes to avoid: [list pitfalls you've seen]
Frequency: [daily / per-job / weekly / as-needed]

Output format:
- Title and version date
- Brief purpose statement
- Required materials / tools
- Numbered step-by-step instructions (clear enough for a new hire)
- Quality check notes after key steps
- Troubleshooting tips section

Document scope changes with clear reasoning for insurance or client approval.

Write a professional change order justification for a restoration project.

Original scope: [brief description of original agreed work]
What changed: [describe the new finding or changed condition]
Why it changed: [what was discovered — hidden damage, code requirement, customer request]
Additional work required: [specific tasks to be added]
Impact on timeline: [how many days added, if any]
Impact on cost: [additional cost or TBD pending estimate]
Supporting evidence: [photos, moisture readings, code references — list what you have]
Project address: [address]
Date of discovery: [date]

Format as a formal change order document with:
- Change order number placeholder
- Clear justification narrative
- Itemized scope additions
- Signature lines for approval

Create job-specific safety briefings for crew before starting work.

Create a job site safety briefing for the crew.

Job type: [water mitigation / fire restoration / mold remediation / demolition / reconstruction]
Job address: [address]
Date: [date]
Known hazards: [list any known issues — asbestos, structural damage, electrical, standing water, etc.]
PPE required: [list — respirators, gloves, tyvek suits, hard hats, etc.]
Equipment being used today: [list — dehumidifiers, air scrubbers, demo tools, etc.]
Emergency contact: [name and phone]
Nearest hospital: [name and address if known]

Output:
- Clear, concise safety briefing (1 page max)
- Hazard awareness section
- PPE requirements checklist
- Emergency procedures
- Sign-off line for crew acknowledgment

Turn rough meeting notes into clean, shareable minutes with action items.

Turn my rough notes into professional meeting minutes.

Meeting type: [team sync / client call / insurance review / project kickoff]
Date: [date]
Attendees: [names + roles]
Rough notes:
[PASTE YOUR RAW NOTES HERE]

Format as:
- **Meeting Header** (type, date, attendees)
- **Key Discussion Points** (organized by topic)
- **Decisions Made** (who decided what)
- **Action Items** (owner + due date for each)
- **Next Meeting** (date if mentioned)

Keep it concise — this should be easy to skim.

Generate talking points, smart questions, and potential objections before any call.

Help me prepare for an upcoming meeting.

Meeting type: [client call / adjuster meeting / team planning / vendor negotiation]
Who will be there: [names and roles]
My goal for this meeting: [what I want to walk away with]
Context: [relevant history, open issues, recent developments]
My concerns: [things I'm worried about — optional]

Give me:
1. **5-7 smart questions** to ask during the meeting
2. **Key talking points** I should cover
3. **Objections to anticipate** and how to respond
4. **Suggested closing ask** — what to request at the end

Think through blockers or tough decisions using structured tradeoff analysis.

I need help thinking through a problem.

Situation: [what's happening — be specific]
What I've already tried: [list any attempts or partial solutions]
Ideal outcome: [what "solved" looks like]
Constraints: [budget, timeline, people, politics, etc.]

Guide me through:
1. **Clarifying questions** — help me see what I might be missing
2. **2-3 possible approaches** — different ways to tackle this
3. **Pros and cons** of each approach
4. **Recommended next step** — what should I do first?

Compile your week into a professional status report for leadership or clients.

Create a professional weekly status report.

Week of: [date range]
My role: [your role at Palm Build]
Projects I'm working on:
- [Project 1]: [brief status]
- [Project 2]: [brief status]
- [Project 3]: [brief status]

Key accomplishments this week:
- [list 3-5 things you completed]

Blockers or issues:
- [list anything slowing you down]

Plan for next week:
- [list top priorities]

Format as a clean, scannable report that leadership can read in under 2 minutes.

Record important decisions with context so the team remembers why choices were made.

Create a decision log entry for an important choice we made.

Decision: [what was decided — one sentence]
Date: [when it was decided]
Decision maker(s): [who made the call]
Context: [why this decision came up — what problem were we solving?]
Options considered:
- Option A: [description]
- Option B: [description]
- Option C: [description, if applicable]
Why we chose this: [reasoning]
Risks or tradeoffs: [what could go wrong, what we're giving up]
Review date: [when should we revisit this? — optional]

Format as a clean, structured log entry that anyone on the team can reference later.

Research a new market, service area, or business opportunity before committing resources.

Help me research a potential business opportunity for Palm Build.

What we're considering: [new service, new market area, new product, etc.]
Current situation: [what we do now, where we operate]
Why we're interested: [what triggered this — customer demand, competitor, opportunity]
Budget range: [if applicable]
Timeline for decision: [when do we need to decide?]

Research and give me:
1. **Market Overview** — size, trends, key players in this space
2. **Opportunity Assessment** — is there real demand? What evidence supports it?
3. **Competitive Landscape** — who else does this? What's their pricing/approach?
4. **Barriers to Entry** — what would it take for us to start?
5. **Risks** — what could go wrong?
6. **Recommendation** — should we pursue this? What's the smart first step?

Note: Use your knowledge but flag anything that should be verified with current local data.

Compare vendors, suppliers, or software options side-by-side for purchasing decisions.

Help me compare options for a purchasing decision.

What I need: [product, service, or software — e.g., "project management software" or "drying equipment supplier"]
Options I'm considering:
- Option A: [name + any details you know]
- Option B: [name + any details you know]
- Option C: [name + any details you know — optional]

Evaluation criteria (prioritize these):
- [criterion 1 — e.g., price]
- [criterion 2 — e.g., reliability]
- [criterion 3 — e.g., customer support]
- [criterion 4 — e.g., integration with existing tools]

Budget: [range if applicable]
Must-haves: [non-negotiable requirements]

Output:
- Comparison table (options as columns, criteria as rows)
- Pros and cons for each
- Recommended choice with reasoning

Analyze whether a proposed investment, hire, or change is worth the cost.

Help me think through the costs and benefits of a business decision.

The decision: [what we're considering — e.g., hiring a new PM, buying equipment, adding a service line]
Estimated cost: [upfront + ongoing if applicable]
Expected benefit: [revenue, time saved, quality improvement, etc.]
Timeframe: [over what period should we evaluate this?]
Current pain point: [what problem does this solve?]
Alternatives: [what happens if we don't do this?]

Analyze:
1. **Direct Costs** — upfront investment, recurring costs, hidden costs
2. **Direct Benefits** — revenue impact, cost savings, efficiency gains
3. **Indirect Benefits** — team morale, customer satisfaction, competitive advantage
4. **Risks** — what could reduce the expected benefit?
5. **Break-even Analysis** — when does this pay for itself?
6. **Recommendation** — go, no-go, or conditional (with what conditions)

Present findings in a format I could share with leadership.

Create compelling job postings that attract the right candidates for restoration roles.

Write a job posting for Palm Build.

Position: [title — e.g., Water Mitigation Technician, Project Manager, Estimator]
Location: [city/area]
Employment type: [full-time / part-time / contract]
Experience required: [years and type]
Key responsibilities:
- [responsibility 1]
- [responsibility 2]
- [responsibility 3]
Must-have qualifications: [certifications, licenses, skills]
Nice-to-have: [bonus qualifications]
Salary range: [if sharing publicly]
Benefits highlights: [list key perks]
What makes Palm Build different: [culture, growth, team, mission]

Tone: Professional but human — we want skilled people who are also good teammates.

Output:
- Attention-grabbing headline
- Company intro (2-3 sentences)
- Role summary
- Responsibilities list
- Qualifications (required + preferred)
- Benefits section
- How to apply

Prepare role-specific interview questions that reveal real capability and culture fit.

Generate interview questions for a candidate at Palm Build.

Role: [position title]
Experience level: [entry / mid / senior]
Key skills we need: [list 3-5 critical skills]
Team they'd join: [describe the team dynamic]
Our biggest concern: [what's the risk of a bad hire in this role?]

Generate:
1. **5 Technical/Role Questions** — test whether they can actually do the work
2. **3 Behavioral Questions** — "Tell me about a time when…" format
3. **2 Culture Fit Questions** — do they align with how Palm Build works?
4. **2 Situational Questions** — hypothetical job scenarios specific to restoration
5. **What to listen for** — brief notes on what a strong answer sounds like for each question

Draft structured, fair performance reviews that are specific and actionable.

Help me write a performance review for a team member.

Employee name: [name]
Role: [title]
Review period: [date range]
Overall performance: [exceeding / meeting / below expectations]

Strengths (things they do well):
- [strength 1]
- [strength 2]
- [strength 3]

Areas for improvement:
- [area 1]
- [area 2]

Key accomplishments this period:
- [accomplishment 1]
- [accomplishment 2]

Any concerns: [attendance, attitude, quality, safety — be specific]

Write a professional performance review that is:
- Specific (reference actual behaviors and results, not vague traits)
- Balanced (honest about both strengths and growth areas)
- Actionable (clear next steps for development)
- Respectful (firm but fair in tone)

Include:
- Summary paragraph
- Strengths section
- Areas for growth with specific suggestions
- Goals for next period
- Overall rating recommendation

Create a structured onboarding plan so new hires get up to speed fast.

Create a new hire onboarding checklist for Palm Build.

New hire role: [title]
Department: [operations / admin / sales / field]
Start date: [date]
Direct manager: [name]
Buddy/mentor assigned: [name — optional]

Include checklist items for:
1. **Before Day 1** — what to prepare before they arrive
2. **Day 1** — orientation, introductions, setup
3. **Week 1** — initial training, shadowing, key meetings
4. **First 30 Days** — deeper training, first solo tasks, check-ins
5. **First 90 Days** — performance expectations, independence milestones

For each section, list:
- Specific tasks with who is responsible
- Required paperwork or credentials
- Tools/systems to set up (email, software, equipment)
- Key people to meet
- Training materials to review

Condense a complex project, proposal, or initiative into a 1-page summary for leadership.

Write an executive summary for leadership at Palm Build.

Topic: [project name / proposal / initiative]
Audience: [who will read this — owner, leadership team, board, investor]
Full context:
[PASTE the longer document, notes, or details here — or describe in detail]

Write a 1-page executive summary that includes:
1. **Overview** — what this is about in 2-3 sentences
2. **Key Findings / Highlights** — the 3-5 most important points
3. **Financial Impact** — costs, savings, or revenue implications (if applicable)
4. **Recommendation** — what action should be taken
5. **Timeline** — key dates and milestones
6. **Next Steps** — what needs to happen immediately

Keep it scannable — busy leaders should get the full picture in under 2 minutes.

Create a structured project timeline with phases, milestones, and dependencies.

Build a project timeline for a Palm Build job.

Project: [name or description]
Project type: [water mitigation / fire restoration / full reconstruction / etc.]
Start date: [date]
Target completion: [date]
Key phases:
- [Phase 1 — e.g., Assessment & Documentation]
- [Phase 2 — e.g., Mitigation / Demo]
- [Phase 3 — e.g., Reconstruction]
- [Phase 4 — e.g., Final Inspection & Closeout]

Key milestones to track:
- [milestone 1 — e.g., insurance approval]
- [milestone 2 — e.g., materials ordered]
- [milestone 3 — e.g., final walkthrough]

Known constraints: [weather, permits, insurance delays, material lead times, etc.]
Team size: [number of crew members]

Output:
- Phase-by-phase timeline with estimated durations
- Key milestones with target dates
- Dependencies (what must finish before the next phase starts)
- Buffer time recommendations
- Risk flags for potential delays

Identify and evaluate project risks before they become problems.

Create a risk assessment for a Palm Build project.

Project: [name / description]
Project type: [restoration type]
Location: [address]
Estimated value: [dollar amount if known]
Duration: [expected timeline]
Stakeholders: [homeowner, insurance carrier, PM, subs, etc.]

Known concerns:
- [concern 1]
- [concern 2]
- [concern 3]

For each risk identified, provide:
1. **Risk Description** — what could go wrong
2. **Likelihood** — Low / Medium / High
3. **Impact** — Low / Medium / High
4. **Mitigation Strategy** — how to prevent or reduce it
5. **Contingency Plan** — what to do if it happens
6. **Owner** — who is responsible for monitoring

Include these risk categories:
- Safety & health
- Scope creep
- Budget overruns
- Timeline delays
- Insurance/approval issues
- Subcontractor reliability
- Weather/environmental

Output as a professional risk assessment document with a summary risk matrix.

Polish any text for grammar, clarity, and professional tone before sending.

Review and improve this text for grammar, clarity, and professional tone.

Text:
[PASTE YOUR TEXT HERE]

Audience: [customer / adjuster / internal team / leadership]
Desired tone: [professional / friendly / formal / casual]

Output:
1. **Corrected version** — fix grammar, spelling, punctuation, and awkward phrasing
2. **Changes made** — brief list of what you fixed and why
3. **Tone check** — does it match the requested tone? Any adjustments?

Don't rewrite from scratch — keep my voice, just clean it up.

Generate ideas quickly when you are stuck or need creative options.

I need help brainstorming. Don't hold back — give me volume.

Topic: [what am I trying to solve, create, or improve?]
Context: [relevant background — industry, constraints, audience]
What I've already considered: [list anything you've thought of]
Direction I'm leaning: [if you have a preference — optional]

Give me:
1. **10 ideas** — ranging from safe/practical to creative/bold
2. **Top 3 picks** — your recommendation with brief reasoning for each
3. **Wild card** — one idea that's unconventional but could work

For each idea, give a 1-sentence description so I can quickly scan.

Simplify complex concepts into plain language anyone can understand.

Explain this concept in plain, simple language — like I'm smart but not an expert in this area.

Concept or topic:
[PASTE or describe the complex thing here]

My audience: [who am I explaining this to? — homeowner, new hire, leadership, adjuster]
Why they need to understand: [what decision or action depends on this?]

Output:
1. **Simple explanation** — 3-5 sentences, no jargon
2. **Analogy** — a relatable comparison to everyday life
3. **Key takeaway** — the one thing they need to remember
4. **Common misconception** — what people usually get wrong about this

Turn messy data, lists, or notes into clean tables, CSVs, or structured formats.

Organize this messy data into a clean, usable format.

Raw data:
[PASTE YOUR MESSY DATA, LIST, OR NOTES HERE]

Desired output format: [table / CSV / bullet list / numbered list / JSON]
Sort by: [alphabetical / date / category / priority — optional]
Group by: [any grouping criteria — optional]

Additional instructions:
- Remove duplicates if any
- Flag anything that looks incomplete or inconsistent
- Add headers/labels where appropriate

Output the clean formatted version, then briefly note any issues found in the source data.