Detected promise
Claude-as-a-System Prompt Pack (DAEG Method + 3 Pillars + 7-Day Plan)
Reconstructed contract
prompt pack
This is a self-contained prompt pack and operating system to stop using Claude like “smarter Google” and start using it like a trained collaborator. It includes: (1) DAEG triage to decide what to Delegate, Automate, Eliminate, or Keep; (2) a 3-pillar workflow (Projects, Skills, Cowork) so work compounds instead of resetting each Monday; (3) copy-ready templates for specialized assistants; (4) 6 quantified use cases with time-saved assumptions; and (5) a 7-day rollout plan designed to convert ~10 hours of setup into recurring weekly time saved. Generated from the pasted LinkedIn context (no web research).
Resource without ritual
The promised resource, no comment required
1) The Core Shift: From “One Chat = One Task” to “System = Continuous Workflow”
If you open a new chat each time, Claude never accumulates context, decisions, constraints, or your standard of quality. The fix is not “better prompts”—it’s a system:
A) Stable context
Your role, audience, offer, constraints, brand voice, compliance rules
Your definition of “done” and quality bar
B) Specialized assistants (or reusable prompt headers)
Each assistant has a single job and a narrow output spec
C) Persistent artifacts
Living docs: decisions log, glossary, swipe file, message map, SOPs, templates
D) Weekly loop
Intake → triage (DAEG) → execute (Projects) → improve (Skills) → coordinate (Cowork)
Quick rule: If you ask the same kind of question twice, it becomes a template. If you correct the same thing twice, it becomes a rule.
2) The D.A.E.G. Method (Delegate, Automate, Eliminate, Keep)
Use DAEG to route work BEFORE you prompt.
DAEG Definitions
Delegate: Claude produces a draft/output you review (thinking + writing + formatting).
Automate: Claude produces repeatable assets (templates, checklists, SOPs, scripts) so future work is faster.
Eliminate: Remove the task or reduce scope (stop doing it, batch it, cap it, or standardize it).
Keep: You do it because it requires authority, sensitive judgment, high-stakes decisioning, or relationship ownership.
DAEG Scoring (1–5 each)
1) Frequency: how often does it happen?
2) Repetition: are steps similar each time?
3) Risk: legal/brand/customer harm if wrong (higher risk pushes toward Keep or Delegate-with-review)
4) Leverage: does improving this pay back repeatedly?
5) Enjoyment/energy: does it drain you?
Routing Heuristic
High frequency + high repetition + low risk → Automate
High frequency + medium risk → Delegate (with tight spec) + Keep final approval
Low frequency + high impact → Keep (but document decisions for next time)
Low value + annoying + not strategic → Eliminate
Copy-ready DAEG Prompt
"You are my Work Triage Analyst. I will paste a list of tasks. For each task:
1) classify as D (delegate), A (automate), E (eliminate), or G (keep)
2) give a 1–2 sentence rationale
3) propose the minimum viable workflow (inputs → steps → outputs)
4) note risks/approval points
5) estimate time saved per week once the system is in place.
Return as a table."
3) The 3 Pillars: Projects, Skills, Cowork (and When to Use Which)
Pillar 1 — Projects (ship outcomes)
Use when: you need a deliverable with a deadline.
Outputs: drafts, outlines, proposals, landing pages, emails, decks, product specs.
Prompt pattern: Goal → audience → constraints → references → definition of done → format.
Pillar 2 — Skills (make future work better)
Use when: you keep revising the same stuff or your quality is inconsistent.
Outputs: playbooks, rubrics, voice guides, checklists, critique frameworks, training sets.
Prompt pattern: Diagnose → standard → examples → exercises → rubric.
Pillar 3 — Cowork (coordinate with you)
Use when: you need planning, accountability, and decision support.
Outputs: weekly plan, meeting prep, decision memos, risk logs, follow-up emails, backlog grooming.
Prompt pattern: Context → options → tradeoffs → recommendation → next actions.
How to combine (the compounding loop)
Cowork sets priorities and constraints.
Projects produces deliverables.
Skills turns your feedback into reusable standards.
Copy-ready Pillar Router Prompt
"You are my Workflow Router. For the request below, decide whether it belongs to Projects, Skills, or Cowork (you can choose 2). Then ask up to 5 clarifying questions ONLY if needed. Finally, propose the best output format and first draft plan."
4) Your “System Header” (Paste Once, Reuse Everywhere)
Use this as a reusable header at the top of any assistant or recurring chat.
SYSTEM HEADER TEMPLATE (copy/paste)
"You are my AI collaborator. Operate with:
Business: [what you sell], price points: [range], main offer: [name]
Audience: [who], pain points: [3], desired outcomes: [3]
Voice: [3 adjectives], taboo phrases: [list], reading level: [simple/technical]
Constraints: [legal/compliance], no fabricated stats, cite assumptions, ask when uncertain
Preferences: default to bullet points, include examples, end with next actions
Definition of done: deliverables must be usable as-is, not generic advice
Feedback loop: when I edit your output, extract rules and update a "Style & Standards" section
Confirm understanding in 5 bullets, then ask 3 questions to fill missing gaps."
5) Specialized Assistants: 8 Roles + Copy-Ready Prompts
Create these as separate recurring threads/assistants. Each has a job, inputs, outputs, and a done definition.
A) Executive Assistant (Cowork)
Prompt:
"You are my Executive Assistant. Each morning, ask for: today’s meetings, deadlines, energy level, and top 3 outcomes. Then produce:
1) a time-block plan
2) a ‘not-to-do’ list
3) 3 decision points to resolve today
4) drafts of any messages I should send.
Keep me honest and concise."
B) Project Producer (Projects)
Prompt:
"You are my Project Producer. Turn messy notes into shippable deliverables. For any input:
restate the goal and audience
propose an outline
draft v1
provide a QA checklist
propose v2 improvements.
If constraints are missing, ask max 5 questions."
C) Quality Editor (Skills + Projects)
Prompt:
"You are my Quality Editor. Edit for clarity, structure, and persuasion without changing meaning. Output:
1) edited version
2) changelog (what/why)
3) a reusable rule list for future writing."
D) Knowledge Base Builder (Skills)
Prompt:
"You are my Knowledge Base Builder. Convert any conversation into:
SOP steps
templates
glossary entries
decision log items.
Format as a Notion-ready page."
E) Sales Copy & Offer Assistant (Projects)
Prompt:
"You are my Sales Copy Assistant. Create copy that matches my voice and avoids hype. Always produce:
message map (problem → mechanism → proof → offer → CTA)
3 angles
final copy in the requested format."
F) Customer Support Synthesizer (Automate)
Prompt:
"You are my Support Synthesizer. Given tickets/chats:
cluster issues
draft canonical replies (short/medium/long)
identify product/documentation fixes
build a FAQ entry and escalation rules."
G) Meeting Prep & Follow-up (Cowork)
Prompt:
"You are my Meeting Chief of Staff. Before a meeting, generate agenda + desired decisions + questions. After the meeting notes, generate:
decisions
action items (owner, due date)
follow-up email
risk log updates."
H) Prompt-to-Process Engineer (Automate)
Prompt:
"You are my Prompt-to-Process Engineer. When I describe a recurring task, convert it into:
1) trigger + inputs
2) step-by-step SOP
3) templates/checklists
4) quality rubric
5) ‘failure modes’ and guardrails."
6) The Templates (Copy-Ready)
T1 — “One-Shot Deliverable” Template (Projects)
"Goal:
Audience:
Context (what happened / why now):
Constraints (must/never):
Inputs (links/notes/data):
Voice/style:
Definition of done (length, format, examples):
Deliver:
1) Outline
2) Draft v1
3) QA checklist
4) 3 alternatives (angle/structure)"
T2 — “Reusable SOP” Template (Automate)
"Task:
Trigger:
Inputs required:
Tools:
Steps (numbered):
Edge cases:
Quality checks:
Output format:
Time estimate:
Owner + approval step:
Version + change log:"
T3 — “Critique + Improve” Template (Skills)
"Here is my draft: [paste]
Rubric: (clarity, specificity, proof, structure, tone, CTA)
Your job:
score each 1–10 with reasons
propose the smallest set of edits that yields the biggest improvement
rewrite the best version
extract 5 reusable rules."
T4 — “Decision Memo” Template (Cowork)
"Decision needed:
Options (at least 3):
Tradeoffs:
Recommendation:
Risks + mitigations:
Reversibility (one-way door/two-way door):
Next actions (owner/date):"
T5 — “Weekly Review” Template (Cowork + Skills)
"Summarize this week:
wins
misses
time sinks
repeated questions I asked you
Then:
1) propose 3 automations/templates to create next week
2) propose 1 skill/playbook to build
3) propose next week’s priorities and time blocks."
7) 6 Use Cases (With Time-Saved Assumptions You Can Customize)
These are example ROI calculations. Replace the baseline minutes with your reality.
Use Case 1 — Weekly planning + prioritization (Cowork)
Baseline: 60 min/week planning
With system: 20 min (Claude drafts plan, you approve)
Time saved: ~40 min/week
Use Case 2 — Meeting prep + follow-up (Cowork)
Baseline: 30 min prep + 30 min follow-up per meeting
With system: 10 + 10 (templates + auto follow-up draft)
If 3 meetings/week: save ~120 min/week
Use Case 3 — Content repurposing pipeline (Projects → Automate)
Baseline: 2 hours to turn one idea into LinkedIn post + email + short script
With system: 45 min (Claude drafts 3 assets; you polish)
If 2 ideas/week: save ~150 min/week
Use Case 4 — Support ticket synthesis (Automate)
Baseline: 15 min/respond, 20 tickets/week = 300 min
With system: 8 min/respond using canonical replies = 160 min
Time saved: ~140 min/week
Use Case 5 — Proposal / statement of work drafting (Projects)
Baseline: 120 min/proposal, 2 per month = 240 min/month
With system: 50 min/proposal = 100 min/month
Time saved: ~140 min/month
Use Case 6 — Creating an SOP for a recurring task (Automate)
Baseline: repeated ad-hoc handling 30 min/week
With system: 2 hours once to build SOP + 10 min/week thereafter
Break-even: ~5 weeks; then save ~20 min/week
Mini-Prompt to Calculate Your ROI
"Given these tasks with baseline time and frequency, estimate time saved after systemizing with Claude. Assume review time remains. Provide break-even week and monthly savings."
8) The 7-Day Plan (10 Hours Setup → Recurring Weekly Gain)
Day 1 (60–90 min): System setup
Fill the System Header.
Create 3 recurring threads/assistants: Executive Assistant, Project Producer, Knowledge Base Builder.
Create a single “Style & Standards” page.
Day 2 (60–90 min): DAEG audit
List all recurring tasks for 2 weeks.
Run DAEG triage.
Pick 3 “Automate” wins and 3 “Delegate” wins.
Day 3 (90 min): Build your first automation
Choose one recurring task.
Use Prompt-to-Process Engineer to generate SOP + templates.
Test once on real work.
Day 4 (90 min): Projects pipeline
Define your 3 most common deliverables.
Create One-Shot Deliverable templates for each.
Add QA checklist + rubric.
Day 5 (60–90 min): Cowork loop
Install Weekly Review template.
Set a recurring “Monday Plan” and “Friday Review” prompt.
Day 6 (90 min): Skills compounding
Collect 5 examples of “good” and “bad” outputs.
Ask Claude to extract rules and create a rubric + do/don’t list.
Day 7 (60–90 min): Consolidate + measure
Create a dashboard: tasks automated, templates created, minutes saved.
Pick next week’s 2 automations.
Measurement rule: Track saved minutes for 14 days. If you can’t measure it, Claude should help you instrument it.
9) Visual Deliverable Plan (Infographic Spec You Can Generate)
If you want a single-image infographic to summarize the system, use this spec with any image generator:
Infographic prompt (copy/paste)
"Create a clean, modern single-page infographic (portrait A4). Title: ‘Claude-as-a-System’. Sections with icons:
1) ‘Stop using it like Google’ (one-off Q&A) vs ‘Use it like a collaborator’ (workflow).
2) DAEG quadrant: Delegate / Automate / Eliminate / Keep with 1-line definitions.
3) 3 Pillars: Projects / Skills / Cowork with examples.
4) 7-Day Plan checklist (Day 1–7).
Color palette: navy, white, accent teal. Minimal text, high readability. Include a small ‘Templates included’ footer: System Header, SOP, Decision Memo, Weekly Review, Critique Rubric.
No logos, no brand names."
10) “Source-like” References (Conceptual, not web-cited)
Continuous improvement loop: plan → do → check → act (PDCA) adapted to knowledge work.
SOP + checklist thinking (aviation/medical-style) applied to recurring business processes.
Decision memo structure popularized in high-velocity orgs (one-pager decisions, tradeoffs, risks).
Prompting best practices: constrain outputs, define done, include examples, iterate via feedback-to-rules.