Plan a new task

Feature: $ARGUMENTS

Resolve the input first

$ARGUMENTS is either a tracker ticket (a key like ACC-30, or a Jira / Linear / GitHub issue URL) or a free-form feature description. Tell them apart and handle each:

• A ticket (a key such as ABC-123, or an issue URL): fetch it from the tracker before you plan (Jira via the Atlassian MCP, GitHub via gh issue view, etc.). Read its summary, acceptance criteria, and per-ticket context. Then follow its links up to the epic and the epic's linked architecture page (Confluence via the Atlassian MCP) and inherit those decisions (see "Inherit, don't re-decide" below). Never plan from the bare key; the ticket body plus its epic and architecture are the real input.
• A free-form description: plan directly from it (greenfield or ad-hoc), asking clarifying questions as needed.

Mission

Transform a feature request into a comprehensive implementation plan through systematic codebase analysis, external research, and strategic planning.