Scout a project for contributions

One project per run. The run's Multica sub-issue names the project (owner/repo) and scopes the work. The deliverable is a single comment on that sub-issue.

Scope

• In: investigate candidate contributions likely to be merged; prepare a high-level plan for the top candidate(s); evaluate feasibility.
• Out (hard): forking the repo, making the actual code changes, submitting the PR. Those happen afterwards, after the contribution has been confirmed.

Tooling

MCP-first, gh as fallback. Use the GitHub MCP tools for what they cover (repo metadata, issue and pull-request search, file contents, issue comment threads). Use gh for what MCP does not offer. Keep responses bounded — read only the fields and threads the analysis needs; never JSON-dump whole API responses into the conversation.