ai · $29 · digital download · instant ZIP

Buy now — use today

Outcome: Run 8 copy-paste agent recipes for briefs, proposals, and delivery

For: Operators using Cursor who want client-ready workflows

ZIP download right after PayPal (success page)
Full guide in Markdown + printable HTML (Print to PDF)
extras/: START HERE, swipe templates, worked examples, worksheets, 30-day plan, FAQ
Pays for itself if it saves ~1–2 hours or helps close one small upsell

Buy with PayPal — $29

After payment: instant ZIP with the full guide plus an extras folder (templates, examples, worksheets, 30-day plan).

Digital download · keep your PayPal receipt · no login required

Cursor + MCP Freelancer Recipe Pack

Price: $29 USD · Format: 8 copy-paste agent recipes · Delivery: Instant after PayPal

Who this is for

Operators using Cursor (and optionally MCP tools) who want client-ready workflows — not generic “prompt art.”

Outcome

Run eight recipes for briefs, proposals, delivery QA, and weekly status without reinventing instructions each time.

How to run a recipe in Cursor

Open a workspace folder for the client
Start Agent/Chat
Paste recipe + your inputs
Save outputs into /delivery or /sales
Edit for accuracy before sending to clients

Recipe 1 — Discovery notes → project brief

Turn raw notes into: Goal, Audience, Deliverables, Constraints, Milestones, Risks, Open questions. Client-ready tone.

Recipe 2 — Competitor scan brief

Given 3 competitor URLs/notes, produce: positioning table, gaps, opportunities, recommended differentiator for my offer.

Recipe 3 — Proposal draft from brief

Using the brief, draft Good/Better/Best proposal sections with timeline and assumptions. Don’t invent metrics.

Recipe 4 — SOP writer

Convert my messy process notes into a numbered SOP with inputs, steps, definition of done, and failure modes.

Recipe 5 — QA checklist before delivery

Create a QA checklist for {{deliverable_type}} with critical / major / minor severity. Include client-facing handoff notes.

Recipe 6 — Delivery note

Write a delivery email: what’s included, how to use, known limits, next recommended step (retainer/phase 2).

Recipe 7 — Case study draft

From project folder notes, draft Context → Challenge → Approach → Results (TBD if unknown) → Testimonial ask.

Recipe 8 — Weekly status

Summarize progress this week: done, in progress, blockers, decisions needed, next week plan. Keep under 200 words.

MCP-aware tips

If browser MCP is available: fetch competitor pages before Recipe 2
If repo tools available: ask agent to inspect files before QA
Never let the agent email clients directly without your review

Quality guardrails (include in every run)

No fake testimonials
Mark unknowns as TBD
Prefer bullets over fluff
Ask me clarifying questions if inputs are thin

Example input block

Client: {{}}

Niche: {{}}

Offer: {{}}

Raw notes: {{}}

Constraints: {{}}

ROI

Saving 30–60 minutes per client touch compounds across a month of projects. One cleaner proposal can win the project that pays for this pack many times.

Delivery

All 8 recipes with run instructions after PayPal.

Bonus deep library (included in your ZIP)

ZIP extras include full paste-ready recipe prompts, a worked run, guardrails, and a 30-day agent habit plan.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ultra-detailed appendix

Workspace layout per client

/client-name/notes.md

/client-name/brief.md

/client-name/sales/

/client-name/delivery/

/client-name/qa.md

Recipe order for a new project

1 → 3 → (build) → 5 → 6 → 8 weekly → 7 at end

MCP usage policy

Browser MCP: research only, cite sources

Repo tools: QA against real files

Never auto-send external messages

Evaluation rubric for agent output

Useful? Accurate? Client-safe? Short enough? If any “no,” regenerate with tighter constraints.

Ready? Get the ZIP

Run 8 copy-paste agent recipes for briefs, proposals, and delivery — $29 one-time.

Buy with PayPal — $29

After payment: instant ZIP with the full guide plus an extras folder (templates, examples, worksheets, 30-day plan).

Compare all 50 packs · How delivery works