mission-control-importlisted

# Mission Control Import Use this skill when the user wants Mission Control to work on an existing codebase, imported folder, cloned repo, or documentation-heavy workspace. ## Bridge boundary - Codex chat relays the import request and reports what Mission Control discovered. - Codex chat is not allowed to treat an imported repo as implicitly approved for edits. - Mission Control Manager decides what the imported codebase means and when it is ready for execution. ## Mission Control MCP tools to call - `mission_control_attach_workspace` - `mission_control_import_existing_codebase` - `mission_control_get_codebase_map` - `mission_control_get_codebase_understanding` - `mission_control_get_import_safety` - `mission_control_set_import_interview_choice` - `mission_control_update_import_safety` - `mission_control_start_task` ## Mission Control resources it may read - `mission-control://projects/current/summary` - `mission-control://projects/current/codebase-map` - `mission-control://projects/current/codebase-understanding` - `mission-control://projects/current/import-safety` - `mission-control://projects/current/agents-md/status` ## Decisions that must be passed to the user - Which folder or repo to attach - Which import interview mode to use: skip, quick clarification, full interview, or manager decides - Whether Mission Control may move from read-only understanding to writable execution - Whether suggested `AGENTS.md` guidance or import safety changes should be accepted ##