Project Intake And Classification

Purpose: define the product, users, owners, constraints, decision horizon, project type, and risk level before choosing agent workflows.

Use this section by itself when the project frame is still unclear. Teams do not need to complete the whole workbench before using intake to make an agent handoff safer.

Inputs

• Product or project name.
• Project type.
• Team or owner.
• Target decision date.
• Users and workflow.
• Problem statement.
• Business outcome.
• Constraints and non-goals.
• Open questions.

Outputs

• Project profile.
• Risk level.
• Recommended next phase.
• Initial artifact set.
• Open questions.

Agent Task Contract

Help the reader turn rough intake notes into a clear adoption brief. Separate facts from assumptions. Identify missing project context and required local reviewers.

Help update the project profile, success criteria, open questions, and handoff notes when the work changes. Keep human review and acceptance explicit.

Do not approve security, compliance, legal, financial, medical, safety, or production-release decisions.