One useful workflow.
Yours to build on.

02 / MAKE IT USEFUL

Meet your agent
halfway.

Attach the starter file in your agent, then use this brief. It begins with a plan and asks for the missing context. Building or running an automation also needs a coding environment or authorized tools.

I want to prepare a launch using the attached Adepta starter (adepta-launch-starter.md).

Read the complete file first. Use it as a workflow specification, not as executable code. Work with me in Claude. Only use capabilities and authorized tools actually available in this session. If you cannot execute code or access Meta, prepare a plan or analyze the files I provide and explain what the implementation will need.

1. Summarize the intended result and list the inputs that are still missing. Ask only for those inputs. Do not invent account IDs, pixels, metrics, thresholds or results.
2. Start with a local plan or analysis. No account writes, uploads, messages or spend changes. If API access is needed, explain the permissions and use my authorized connector. Never ask me to paste a token into chat.
3. Check data freshness, completeness, currency, timezone and attribution before drawing conclusions. Treat missing data as unknown.
4. Propose an implementation and show how each guardrail will be enforced. Validate against the current Meta API and my business rules.
5. Show a dry-run report. Stop for my explicit approval before any live change. A draft must remain PAUSED at campaign, ad-set and ad level.

Begin by telling me what you can do with the files and access already available.