Tips & Best Practices

Writing effective mission objectives

The quality of your mission objective directly impacts your results. Here's what works:

Good objectives:

• "Build a responsive landing page with a hero section, feature grid, pricing table, and contact form using Next.js and Tailwind CSS"
• "Implement JWT-based user authentication with email/password signup, Google OAuth, and password reset flow"
• "Analyze the Q3 sales CSV file, identify the top 5 growth trends, and produce an executive summary with charts"

Vague objectives (avoid):

• "Build a website"
• "Fix the code"
• "Do some research"

Structuring your projects

• One project per initiative — Don't mix unrelated work in the same project.
• Upload context before launching — Give agents the full picture upfront by adding docs to the Vault.
• Use descriptive project names — "Company Website Redesign v2" is better than "Project 1".
• Archive completed projects — Keep your workspace clean and organized.

Getting the best results

• Let the Coordinator drive — Resist micromanaging individual tasks. Provide high-level guidance and let the system orchestrate.
• Review reasoning, not just results — Before approving a Decision Gate, read the agent's Reasoning Stream to catch architectural mistakes early.
• Check Workflows periodically — Catch blocked or failed tasks early.
• Respond to agent questions promptly — Agents pause when they need human input.
• Use Mission Chat for corrections — A simple message redirects the team more effectively than starting over.

Common patterns