Iterate Research Questions

Revise the active research-question artifact in place. The artifact remains a query plan for learning how the codebase works today; this skill does not answer the questions or design the requested change.

1. Resolve the artifact and every revision input

Use an explicit research-question file path when the user supplies one. When only a task identifier is known, resolve its artifact directory under .agent-work/tasks/<task-id>/. When the input is a task directory, or the task directory is available from session context, run ls -La -- <task-directory> so symlinked directories are followed and inspect the listing for research-question documents. Select the sole match. If there are several plausible matches, ask the user to choose before reading them; if there are none, ask for the artifact path.

Read the selected artifact in full, including frontmatter, question numbers, context pointers, retired questions, and revision history. Then inventory all applicable revision inputs:

• feedback in the invocation or conversation;
• supplied <comments>...</comments> blocks, preserving comment IDs and reply order;
• artifact comments fetched through the host when the user asked to apply or review them;
• ticket, task, or collateral files the user explicitly named as feedback sources; and
• changed repository or external evidence the user explicitly called out.

Treat each user-authored comment or reply as a separate input. Read no sibling task artifacts merely because they share the directory. If the user supplied neither revision instructions nor actionable comments, ask what they want changed and stop.