Phase skill: fetch Linear ticket or parse task description into structured context
Load the task context so all subsequent phases have a clear picture of what to build.
If ticket identifier (AGE-XX):
mcp__plugin_linear_linear__get_issue to fetch the full ticketIf plain text description:
Update Linear ticket — assign to self and move to "In Progress" — if the task is a Linear ticket (AGE-XX pattern):
mcp__plugin_linear_linear__save_issue call with both:
state: "In Progress"assignee: "me"assignee: "me" resolves to the authenticated Linear user behind the MCP — safe to call even if already assigned to self (idempotent)In Progress or a later state, but still set the assigneeWrite to state outputs:
{
"ticket_id": "AGE-XX",
"title": "...",
"description": "...",
"labels": [],
"priority": "high|medium|low",
"acceptance_criteria": "..."
}
Initialize the conversation file at .harness/conversations/<task-id>.md (pickup owns file creation):
# <task-id>: <title>
## Pickup
**Ticket:** AGE-XX — <title>
**Priority:** <priority>
**Linear status:** moved to In Progress
**Linear assignee:** self
**Description:** <summary>
<!-- Subsequent phases append their sections below -->
## Harness Issues
<!--
Record any friction encountered during this implementation. Format per issue:
### [Phase] Brief title
- What happened: <attempt and failure>
- Root cause: <why the skill instruction was wrong/missing>
- Workaround: <what you did instead>
- Suggested fix: <specific edit to phase skill>
- Turns wasted: <count>
Leave empty if no friction occurred.
-->