prepare-automation-knowledge

Prepare the KNOWLEDGE an automation/project needs BEFORE any code is written: at planning time explicitly consider the class of external tools (web search like exa.ai, platform APIs like the YouTube API, ready-made skills/MCP connectors found on the internet); default to DELEGATING the build to a coding agent with the fullest possible specification file; and — because coders usually have NO internet — transfer the external documentation they need onto the workspace disk (CRUD-DOCS) + Company Memory with the owner's agreement, token-lean (metadata only, the document body never enters the model context). Sequence: find → agree → transfer → ingest → reference the local paths in the coder's spec file. Via MCP: owner_docs_transfer_external_documentation (:3230).