Research Goal Curator

Workflow

1. Verify that target_dir/AGENT_GOAL.md exists. If it does not, stop and tell the caller to scaffold the workspace first with the appropriate scaffolder (agent-files for generic workspaces, manuscript-revision-agent-files for LaTeX IEEE manuscript revision).
2. Read the existing AGENT_GOAL.md and identify its current sections: statement, scope, non-goals, success criteria, and constraints.
3. Read research_brief and any chat_context, then interact with the user until the research intention is explicit enough to save.
4. When the user has already approved exact wording, preserve that wording unless the user explicitly asks for a revision.
5. Curate the whole AGENT_GOAL.md so the sections are mutually consistent and reflect the same research intention.
6. If dry_run is true, return the proposed update summary without writing. Otherwise update AGENT_GOAL.md and return a concise report of what changed.

Outputs

• goal_path
• written
• summary
• updated_sections
• warnings
• open_questions

Failure / Escalation

• If AGENT_GOAL.md is missing, fail cleanly and route to the appropriate scaffolder: agent-files for generic workspaces, manuscript-revision-agent-files for LaTeX IEEE manuscript revision.
• If the user intention remains ambiguous after refinement, stop with written=false and put the remaining blockers in open_questions.
• If the chat contains conflicting goal statements, ask the user which wording governs before writing.
• If the request expands into broader agent-file editing, state that the other agent files are out of scope for this skill.

Tool Contract

• Read tool.json for the authoritative schema.
• target_dir and research_brief are required.
• chat_context is optional supporting input and should not override explicit user-approved wording.
• Always return the full output envelope even when no write occurs.