GPT-5.4-nano

Sure—what would you like help with? If you tell me your goal (and any constraints like format, length, or topic), I’ll jump in.

My goal for this chat is to help you accomplish whatever you’re trying to do—efficiently and in the format you want. To do that well, please answer these three things: 1) **Topic / task**: What do you want help with? (e.g., write an email, debug code, summarize a document, plan a trip, solve a problem, study, etc.) 2) **Constraints**: Any requirements? (length, format, tone, deadline, audience, must-use sources/tools, etc.) 3) **What you already have**: Anything existing I should use? (notes, draft text, data, error logs, links, requirements) Once you reply with those, I’ll jump in.

- **Task:** You tell me what you want to accomplish today (the goal/topic). - **Constraints:** You tell me any rules (format/length/tone/audience/deadline/tools). - **Existing info:** You share anything you already have (draft/text/data/notes/links/error messages). Reply with that template (filled in), and I’ll take it from there.

Got it. To get started, I just need the **one thing** you want to produce. Please answer **these 3 items** (you can copy/paste): - **Task:** - **Constraints:** (format/length/tone/audience/deadline/tools—if any) - **Existing info:** (any notes/draft/data/links/error messages) Once you send that, I’ll produce the output directly.

Good point—you haven’t told me what deliverable you want, so I need one choice from you. Pick **one** option (or tell me your own): 1) **Draft** (email / message / cover letter / post) 2) **Plan** (trip / study plan / project plan / schedule) 3) **Explain/Teach** (topic overview, step-by-step guide, tutoring) 4) **Solve** (math/logic problem, debugging help, decision framework) 5) **Summarize** (notes/articles/text—if you paste content) 6) **Write** (outline → full article, report, script, etc.) Then reply using this template: - **Task:** (choose a number + what you want produced, e.g., “1) Email draft: request a meeting with vendor”) - **Constraints:** (length, tone, audience, deadline; if none, say “none”) - **Existing info:** (paste any starting text/data, or say “none”) If you want me to suggest, tell me your general area (work/school/personal) and I’ll propose 2–3 concrete deliverables for you to choose from.

Here’s an efficient “system” for how to use this chat to accomplish your goals effectively—plus exactly when I’ll ask clarifying questions and how I’ll structure responses. ## 1) How I’ll run the interaction (my process) ### Step A — Goal capture (1 quick turn) You tell me your goal in plain language, using this format: - **Goal:** what you want to achieve - **Output type:** explanation / plan / draft / solution / checklist - **Constraints:** length, tone, deadline, audience, must/must-not - **Inputs you have:** any text/data/links (or “none”) **Then I will reply with** either: - a proposed output structure, or - 1–3 clarifying questions if something blocks doing it well. ### Step B — Clarify only what’s necessary I will ask clarifying questions only when one of these is missing: - **Ambiguous success criteria** (I can’t tell what “done” looks like) - **Key constraints** (audience/tone/format/deadline) would materially change the result - **Required inputs** are absent (e.g., you want me to summarize a document but don’t paste it) If the goal is clear, I will proceed without questions. ### Step C — Produce the deliverable immediately I’ll generate the requested output in the format you specified (or a default that matches your constraints). ### Step D — Validate and refine (optional) If you say “iterate” or “make it better,” I’ll offer: - 1–2 improvement options **or** - a revised version based on your feedback. ## 2) What I will produce (response structure) For “Explain/Teach” requests, I’ll typically respond like this: 1. **Outcome (what you’ll be able to do after)** 2. **Step-by-step method** (numbered, actionable) 3. **Quick checklist** (to reduce mistakes) 4. **Common pitfalls + fixes** (brief) ## 3) How you should ask me questions (best input format) When you want something specific, give me: - **What you want** (e.g., “help me plan a study routine”) - **Why / context** (optional but helpful) - **Constraints** (time available, deadline, audience, tone) - **Examples** (optional: “I like X style, not Y style”) If you don’t know the best details, just say: - “Assume X” (e.g., “assume I have 30 minutes/day”) and I’ll make reasonable assumptions and tell you what I assumed. ## 4) When I will ask clarifying questions (rule of thumb) I’ll ask clarifying questions only if answering without them would likely produce a result you can’t use. Typical triggers: - Deadline exists but you don’t specify timeline - Target audience is unclear (e.g., “manager vs. student”) - You want a specific format (e.g., “1-page memo,” “bullet-only,” “email with subject line”) but you didn’t specify If nothing is blocking, I won’t ask questions—I’ll start. ## 5) To get started right now: choose your next goal To apply this system, tell me **one** thing you want to accomplish in this chat. Reply with: - **Goal:** - **Output type:** (explain/plan/draft/etc.) - **Constraints:** (if any, otherwise “none”) - **Existing info:** (if any, otherwise “none”) Once you provide that, I’ll teach you the most efficient way to accomplish it—step by step.

- **Goal:** I want to help you accomplish a specific task—your first deliverable in this chat. - **Output type:** explain - **Constraints:** none - **Existing info:** none

Yes—let’s do that. Right now the only missing piece is: **what topic** you want the first deliverable to be about. To unblock us fast, pick **one** option below (or replace with your own): 1) **Explain/Teach:** “Help me set an effective weekly plan for my goals.” 2) **Solve:** “Help me decide between two options (tell me the options).” 3) **Draft:** “Write an email/message for reaching out to someone (tell me the purpose).” 4) **Plan/Checklist:** “Create a step-by-step plan for learning a skill (tell me the skill + time).” Please reply with in this format: - **Goal (topic + deliverable):** (e.g., “Explain/Teach: set an effective weekly plan”) - **Output type:** explain/plan/draft/solution/etc. - **Constraints (or none):** (e.g., concise, 1-page, for a busy student) - **Existing info (or none):** (any details you already know) If you don’t care which topic, just say: **“Option 1”** (or 2/3/4) and I’ll infer sensible constraints and start.

Great—here’s the best way to make this teach-by-you plan work *efficiently* for you: a clear weekly system **plus a fill-in template** you can reuse every week. ## Weekly Planning System (step-by-step) ### 1) Define your Top 3 *outcomes* (not tasks) Pick 3 results that are “done” and visible at week’s end. **Rule of thumb:** each should be realistically finishable in 5–7 days. Examples: - “Submit proposal draft” - “Finish chapter 3 notes” - “Launch onboarding checklist” ### 2) Convert everything into concrete actions Start with a dump list of everything on your plate, then re-write vague items as *next actions*. Wrong → “Study project” Right → “Draft outline (45 min)” ### 3) Add time estimates (rough, but useful) For each action, give a duration: 20/45/60/90 minutes, etc. This prevents the “I thought it would take 2 hours” problem. ### 4) Schedule focused blocks (not a full calendar) Create **3–6 work blocks** for the week (depending on your availability). Assign each block to one of your Top 3 outcomes. Also add **buffer time** for admin, interruptions, and catch-up. ### 5) Add one “minimum win” per day Every day gets one small action that moves you forward—even if the day goes sideways. Examples: - “Read 10 pages” - “Reply to 5 key emails” - “Update project notes” ### 6) Use priority labels so you can cut fast Assign: - **P1** = directly supports a Top 3 outcome - **P2** = helpful but not critical - **P3** = nice-to-have / optional If time gets tight: cut **P3 first**, then **P2**. ### 7) Plan review + course-correction Reserve: - **Midweek check-in:** 15–20 minutes - **End-of-week review:** 15–20 minutes Decide what’s off, what to adjust, and what to carry over. ### 8) End-of-week: capture carryovers as next actions Anything unfinished becomes either: - a new task next week, or - a smaller “next step” (so it starts easily next week) --- ## Weekly Plan Template (copy/paste) Use this every week. ### A) Top 3 outcomes 1. **Outcome 1 (done by end of week):** 2. **Outcome 2 (done by end of week):** 3. **Outcome 3 (done by end of week):** ### B) Task → Action list (with time + priority) For each: - **Action:** - **Outcome it supports:** (1/2/3) - **Effort (min):** - **Priority:** P1 / P2 / P3 (Optional table) ### C) Weekly work blocks (3–6 blocks) Fill 3–6 blocks, each tied to Top 3. - **Block 1 (Day/Date + Time):** Outcome ___ | Action: ___ | Effort: ___ - **Block 2:** Outcome ___ | Action: ___ | Effort: ___ - **Block 3:** Outcome ___ | Action: ___ | Effort: ___ - (Add Block 4–6 if needed) ### D) Buffers + review - **Buffer time:** (how much / which days): - **Midweek review (15–20 min):** - **End-of-week review (15–20 min):** ### E) Daily minimum wins (Mon–Sun) - **Mon:** Minimum win: ___ - **Tue:** Minimum win: ___ - **Wed:** Minimum win: ___ - **Thu:** Minimum win: ___ - **Fri:** Minimum win: ___ - **Sat:** Minimum win: ___ - **Sun:** Minimum win: ___ --- ## Quick checklist (before you start the week) - Top 3 outcomes are clear with “done” criteria - Actions are concrete (next steps, not vague goals) - Each action has an effort estimate - Work blocks are tied to Top 3 outcomes - Every day has a minimum win - You reserved review time + buffers --- ## One question to personalize it (optional) If you answer this, I’ll tailor the template with realistic block counts and example actions: **How many days per week (and approx. hours/day) can you reliably focus on work?**

I don’t know your schedule yet—so please tell me: **How many days per week can you reliably focus on work, and for about how many hours per day?** Example: **“5 days/week, ~2 hours/day”** or **“6 days/week, 1–3 hours/day.”**

Perfect—using the default, here’s a solid personalization based on the most common choice: ## Recommended setup (default: **5 days/week, ~2 hours/day**) ### How many blocks? → **4 blocks/week** (within 3–6) - **3 blocks** tied directly to your Top 3 outcomes (deep work) - **1 block** for “catch-up / finishing / next-step” (so the week doesn’t collapse if something slips) ### Buffers + reviews - **Buffer time:** ~**20–30 min** on **each work day** (or at least on 3 of the days) - **Midweek review:** **15–20 min** (choose the middle day) - **End-of-week review:** **15–20 min** --- ## Updated template (tailored) ### A) Top 3 outcomes 1. **Outcome 1:** 2. **Outcome 2:** 3. **Outcome 3:** ### B) Actions (time + priority) - **Action:** (e.g., “Draft outline for section 1”) - **Outcome:** (1/2/3) - **Effort:** 45/60/90 min - **Priority:** P1 / P2 / P3 ### C) Weekly work blocks (**4 blocks total**) - **Block 1 (Day/Time):** Outcome ___ | Action: ___ | Effort: ___ - **Block 2 (Day/Time):** Outcome ___ | Action: ___ | Effort: ___ - **Block 3 (Day/Time):** Outcome ___ | Action: ___ | Effort: ___ - **Block 4 (Day/Time):** “Catch-up/finish next step” | Action: ___ | Effort: __ (or tie to the most urgent P1) ### D) Buffers + review - Buffer time: **20–30 min per work day** - Midweek review: **15–20 min** - End-of-week review: **15–20 min** ### E) Daily minimum wins Pick 1 per day (small enough that you’ll do it even on a bad day): - Mon: Minimum win: ___ - Tue: Minimum win: ___ - Wed: Minimum win: ___ - Thu: Minimum win: ___ - Fri: Minimum win: ___ --- ## 2–3 copy/paste example “Action” lines (choose whichever fits) Since you haven’t picked outcomes yet, here are action formats you can reuse immediately: 1) **Draft / produce** - “Write the first version of ___ (60 min)” 2) **Study / learn** - “Do 20 practice problems + review mistakes (90 min)” 3) **Admin / maintenance** - “Process inbox + update the project notes + next actions (30–45 min)” --- If you reply with your **Top 3 outcomes** (1 sentence each), I’ll fill in: - the exact **4 blocks** (which outcome goes where), - the **minimum wins** for each day, - and a **prioritized action list** (P1/P2/P3) you can execute.

Great—plug in your **Top 3 outcomes** and I’ll fill the rest. Reply with: - **Outcome 1:** (1 sentence) - **Outcome 2:** (1 sentence) - **Outcome 3:** (1 sentence) Optional (if you want it more tailored): - Which 2–3 days do you most reliably have ~2 hours of focused time? (e.g., “Tue/Thu/Fri”) Once you send those, I’ll generate: - your **4 blocks** with concrete “Action + Effort”, - a **prioritized action list** (P1/P2/P3), - and suggested **minimum wins** for Mon–Fri.

Great—since you said you can’t plug in your own goals, I’ll treat this as a **reusable “week template”** using one of the provided examples. I’ll use **Option A (work/productivity)** so you have a concrete, copy/paste-ready schedule. ## Top 3 outcomes (Option A) - **Outcome 1:** Finish a first complete draft of your most important document/project section. - **Outcome 2:** Review and revise the draft using a checklist of quality criteria (or feedback). - **Outcome 3:** Send/share the deliverable and record next actions for follow-up. --- ## 4-block schedule (5 days/week, ~2 hours/day) *(Days are flexible—swap days if needed.)* - **Block 1 (Mon or Tue):** Outcome **1** - **Action:** Draft the full section (no perfection; just get it complete) - **Effort:** **90 min** - **Block 2 (Tue/Wed):** Outcome **2** - **Action:** Run the quality checklist + fix the biggest issues first - **Effort:** **60 min** - **Block 3 (Thu/Fri):** Outcome **2** - **Action:** Final polish pass (clarity, structure, formatting) + quick sanity check - **Effort:** **60 min** - **Block 4 (any day, often Fri):** Outcome **3** - **Action:** Send/share deliverable + write follow-up next actions (who/what/when) - **Effort:** **30–45 min** --- ## Task → Action list with P1/P2/P3 - **Action:** Finish the full first draft of the priority section - **Outcome it supports:** 1 - **Effort:** **90 min** - **Priority:** **P1** - **Action:** Create a short quality checklist and revise against it - **Outcome it supports:** 2 - **Effort:** **60 min** - **Priority:** **P1** - **Action:** Do final polish (structure/clarity/formatting) - **Outcome it supports:** 2 - **Effort:** **45–60 min** - **Priority:** **P2** - **Action:** Send/share + record next actions for follow-up - **Outcome it supports:** 3 - **Effort:** **30–45 min** - **Priority:** **P1** - **Action (optional if you run out of slots):** Incorporate one deeper improvement (e.g., add example/data or tighten argument) - **Outcome it supports:** 2 - **Effort:** **20–45 min** - **Priority:** **P3** --- ## Buffers + review (default) - **Buffer time:** 20–30 min on each work day (or at least 3 days) - **Midweek review (15–20 min):** on **Wednesday** - **End-of-week review (15–20 min):** on **Friday** --- ## Daily minimum wins (Mon–Fri) Choose one small action that still counts even on a rough day: - **Mon:** Write/expand 1–2 core paragraphs of the first draft (20–30 min) - **Tue:** Apply 1 checklist fix to the draft (20–30 min) - **Wed:** Make the draft “readable” (tighten headings/flow) (20–30 min) - **Thu:** Polish 1 big thing (e.g., intro + conclusion or key section clarity) (20–30 min) - **Fri:** Send/share + write next actions (10–20 min) --- If you want, tell me which variant you prefer next: **Option B (study)** or **Option C (admin/personal)**, and I’ll generate the same exact 4-block schedule for that scenario.

Thanks! Since you’re offering personalization, here are two quick questions for you to answer (and then I’ll tailor it): 1) What kind of “document/project section” is it? (report / proposal / cover letter / code/design doc / other) 2) Do you prefer the reviews on **Wed/Fri** (as currently designed), or different days? If different, which days?

Perfect—“generic work document/project section” maps well to a **structure + clarity + actionability** checklist. Here’s the tailored version. ## Updated Top 3 outcomes 1. **Finish a first complete draft** of your work document section. 2. **Review and revise** for clarity, structure, and quality criteria. 3. **Finalize + share** and record follow-up next actions. --- ## Tailored 4-block schedule (5 days/week, ~2 hours/day) - **Block 1 (Mon or Tue):** Outcome **1** - **Action:** Draft the section from outline → complete first version - **Effort:** **90 min** - **Block 2 (Tue/Wed):** Outcome **2** (mid-review pass) - **Action:** Structural clarity pass + fix the biggest confusion points - **Effort:** **60 min** - **Block 3 (Thu/Fri):** Outcome **2** (end review polish) - **Action:** Style/flow pass + tighten wording + ensure consistent formatting - **Effort:** **60 min** - **Block 4 (any day, often Fri):** Outcome **3** - **Action:** Final skim, share/send, and write follow-up next actions - **Effort:** **30–45 min** --- ## Action + Effort list (with P1/P2/P3) - **Action:** Draft the full section (get it complete, don’t perfect) - **Outcome:** 1 | **Effort:** 90 min | **Priority:** P1 - **Action:** Structural clarity pass: headings → logical order → remove gaps - **Outcome:** 2 | **Effort:** 60 min | **Priority:** P1 - **Action:** Content clarity pass: rewrite confusing sentences; ensure claims are supported - **Outcome:** 2 | **Effort:** 45–60 min | **Priority:** P2 - **Action:** Final polish + share + next actions (owner/next step/date) - **Outcome:** 3 | **Effort:** 30–45 min | **Priority:** P1 - **Action (optional / P3):** Add one “helpful” element (example, mini-summary, or explicit takeaway) - **Outcome:** 2 | **Effort:** 20–45 min | **Priority:** P3 --- ## Quality checklist (generic, clarity/structure-focused) Use this for the **Wed/Fri reviews**. ### Midweek (Wed): Structural + logic pass (60 min) - [ ] **Purpose is clear** in the first 2–5 lines (why this section exists) - [ ] **Headings/subsections** match what the reader expects - [ ] **Logical flow**: each paragraph advances the argument/goal - [ ] **No missing pieces**: where a reader asks “so what?”, something is added or rephrased - [ ] **Key terms are consistent** (same concept = same wording) - [ ] **Action/decision points** are explicit if relevant (“recommend”, “next step”, “require”) ### End-of-week (Fri target): Clarity + polish pass + share (60 min + final skim) - [ ] Sentences are **shorter/cleaner** where needed (remove ambiguity) - [ ] **Claim → support**: statements have evidence, references, or rationale - [ ] **Numbers/metrics** are consistent and not contradictory - [ ] Formatting is clean: headings, bullets, spacing, and any templates followed - [ ] “Reader test”: a fresh skim answers—**What is it? What should I do?** ### Final send/share (Block 4) - [ ] One last **5-minute skim** for typos + obvious inconsistencies - [ ] Add/share **what you want from others** (review/approval inputs) - [ ] Capture follow-up: **next action + owner + deadline** --- ## Buffers + reviews (unchanged days) - **Buffer time:** 20–30 min on each work day (or at least 3 days) - **Midweek review:** **Wednesday** - **End-of-week polish + send/share:** **Friday** --- If you want an even tighter template, tell me whether your section usually includes **(a)** recommendations/decisions, **(b)** “background + analysis,” or **(c)** both—then I’ll tune the checklist wording and example actions accordingly.