# How to work well with Corey

Give Corey the outcome, not the keystrokes - say what "done" looks like and let it plan the steps. Front-load context so it does not have to ask. Hand over the legwork - research, drafts, admin, monitoring - and keep the judgement calls. Anything public, costly or irreversible waits for your yes.

## Steps
1. Lead with the outcome: Tell Corey what you want to be true at the end, not the exact commands. "Give me my morning brief", "map my value engines", "watch these competitors weekly" - it plans the steps and asks only when a decision is yours.
2. Front-load the context: Say who it is for, any constraints and what good looks like, up front. Corey remembers your world between sessions, so the more you tell it once, the less it has to ask again.
3. Hand over the legwork, keep the calls: Research, first drafts, inbox triage, book-keeping pulls and always-on monitoring are Corey's. The judgement - pricing, positioning, who to hire, what to publish - stays yours.
4. Use the approval gate - it is there on purpose: Corey drafts and prepares, then stops for your yes on anything that ships - a blog post, a LinkedIn or company post, a newsletter, a design or pricing decision. It proposes; you dispose.
5. Let it push back: Ask Corey to challenge you. "Push back on this idea" gets you honest critique instead of agreement, so a weak plan gets caught before you build on it.

## FAQ
Q: What does Corey remember between sessions?
A: Corey keeps a working memory of your world - the people, companies and decisions you have told it about - built as compiled facts plus an append-only timeline, and tidied overnight. So you brief it once and it carries that context into every later session, rather than starting cold each time.

Q: What will Corey never do without asking?
A: Anything that ships or cannot be easily undone. Publishing a post, sending a newsletter, a design or pricing decision, moving a domain, deleting production data or a live payment all wait for your explicit approval. Internal drafts, research and mechanical fixes it just gets on with.

Q: How do I give Corey a good instruction?
A: Say the outcome and the context in one go - who it is for, any limits, and what a good result looks like. You do not need special syntax or a set-up project; plain English is the interface. If a step is genuinely yours to decide, Corey pauses and asks rather than guessing.

Q: What should I keep doing myself?
A: The decisions only you can make - the calls on money, direction, hiring and anything you would want to sign off personally. Corey does the work around those calls and brings each one to you cleanly, so your time goes on judgement, not legwork.

Corey does this for you. Start with Corey, 28 days on us: https://getcorey.ai/get-started