Kickoff alignment
Bring the goal, audience, deliverables, timing, and responsibilities into one shared starting document.
Use this scenarioDescribe the outcome, audience, context, and constraints. MiniMax Code turns them into an editable project brief with clear project scope, deliverables, and open questions.
Describe the project in plain language or start from a common brief scenario.
Brief examples
Choose a starting point
Use the same brief structure to align different teams without pretending every project has the same requirements.
Bring the goal, audience, deliverables, timing, and responsibilities into one shared starting document.
Use this scenarioSummarize decisions, trade-offs, constraints, and information that still needs approval before execution.
Use this scenarioExplain the context and expected output clearly enough for an external partner to estimate and respond.
Use this scenarioDocument the chosen direction, alternatives considered, assumptions, risks, and follow-up actions.
Use this scenarioStart with what is known, keep uncertainty visible, and finish with a document the team can review.
State what the project should change, who it is for, and how the team will recognize a useful result.
Provide the relevant background, timing, dependencies, requirements, and known limitations.
Separate what is included, what is excluded, who owns each area, and what must be delivered.
Check uncertain facts, missing decisions, risks, and follow-up actions before sharing the brief.
Practical guidance on inputs, review, customization, and responsible use.
Start with the project goal, target audience, background, expected deliverables, timing, constraints, stakeholders, and any decisions that have already been made. Mark unknown information instead of guessing it.