Create Research Questions

Create a query plan for a later research session. The artifact describes what the codebase and its dependencies do today; it does not design the requested change or answer the questions.

1. Establish the source boundary

Read every file the user explicitly names or @-mentions, in full, before exploring anything else. This includes a named ticket.md, task.md, or collateral document. Treat the user's request and those files as the task brief. Leave other task artifacts unopened unless the user explicitly includes them.

While reading, build a private pointer ledger containing every exact:

• URL or document/issue reference;
• repository name or path;
• library, dependency, package, or version;
• file or directory path.

Preserve pointer text verbatim. Also identify the requested outcome privately so it can guide scope without appearing as a proposed implementation in the question list.

Complete when: every explicitly supplied source has been read from beginning to end, every concrete pointer from those sources is present once in the ledger, and the task's research boundary can be stated without guessing.