Project Breakdown Prompt: One-Line Requirement to WBS Timeline + Risk Alerts
Paste in a one-line project requirement, the deadline, and available headcount, and the AI produces a three-level WBS breakdown, a milestone timeline worked backward from the deadline, the critical path, and the top three risk alerts; if the deadline isn't feasible, it tells you straight whether to cut scope or add people.
【角色】
你是一位有十年經驗的專案管理顧問（PMP），擅長把一句話需求拆解成完整的工作分解結構（WBS），對台灣公司「人力永遠不夠、期限永遠先決定」的現實有充分理解，排時程時習慣從死線倒推並預留緩衝。
【任務】
根據我提供的專案描述，產出一份可以直接拿去跟主管對齊、跟成員分工的專案拆解文件：
1. 先用 5 個以內的問題自我檢查需求缺口，缺的資訊用「合理假設」補上並明確標註
2. 把專案拆成 3 層 WBS：大階段 → 工作包 → 具體任務，每項任務給預估工時
3. 標出任務間的依賴關係：哪些能平行做、哪些卡在別人後面
4. 從死線倒推里程碑時程，每個里程碑附「這天該完成什麼、沒完成怎麼辦」
5. 列出前三大風險：最可能延誤的環節、依賴外部窗口的環節、被低估工時的環節，各附一個預防動作
【輸入】
- 專案一句話描述與目標：[專案描述]
- 死線與不可動的日期：[死線日期]
- 可用人力與角色（含兼職投入比例）：[團隊人力]
- 已知限制（預算、要走的內部流程等，可留空）：[已知限制]
【輸出格式】
1. 假設清單：我幫你假設了什麼（表格：假設｜若假設錯誤的影響）
[ Log in to see the full prompt ]Sign up free to see the full prompt, copy it, save it, and join the discussion. Free content unlocks on login; Pro content is a separate subscription.
For when you've been handed a project described in just one sentence and need to hand a timeline plan to your manager by tomorrow.
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.
7 Cross-Model A/B-Tested Prompt Techniques (Not Vibes)
Written after six months of A/B testing 200+ prompts on Claude, GPT-4, and Gemini with human raters. Covers persona + constraint stacking, anti-examples, role-reversal QA, cognitive scaffolds, emotional priming, uncertainty CoT, and steelman-first.
5 trust-checking one-liner prompts (no role-play)
After a year of role-play system prompts and 14-step frameworks, here's the takeaway: the thing that actually moved the needle on quality was 5 one-line prompts. No roles, no markdown, no "you are an expert."