@crewaiinc

design-task covers crewai task anatomy, expected output specification, single-purpose principle, configuration patterns, guardrails, dependencies, and common mistakes. structured guide with yaml examples and checklist.

getting-started covers crewai project initialization via cli scaffold, architectural abstractions (llm.call vs agent vs crew kickoff), and mandatory file structure setup to avoid common configuration errors.

partial guide to crewai agent design emphasizing task-first thinking and agent minimalism, but lacks actionable procedures for role/goal/backstory definition, llm selection, or tool assignment.

Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent,…