Log work tickets to the Autodesk work log in Obsidian. Use when the user wants to record a completed or in-progress ticket, update an existing entry, or review their work log. Also use when the user invokes /worklog.
Log work to autodesk-work-log.md in the user's Obsidian vault.
$ARGUMENTS — ticket ID and/or description of the work. If empty, ask the user what to log.Get ticket info: If a ticket ID is provided (e.g. ID-63464), use mcp__mcp-atlassian__jira_get_issue to fetch ticket details (summary, status, type, created date). If no ticket ID, ask the user.
Read the existing work log: Use mcp__mcp-obsidian__obsidian_get_file_contents to read autodesk-work-log.md and check if the ticket already exists.
Gather details from the user or context: For each entry, include:
If ticket already exists: Ask the user if they want to update the existing entry or leave it. If updating, preserve existing content and add/modify the changed sections.
If new ticket: Append a new entry under the appropriate team heading using this format:
### TICKET-ID: Short title
**Status:** Status | **Dates:** Date range | **Type:** Type
**Summary:** What was done.
**Skills & Technologies:** Tech1, Tech2, Tech3
**Challenges & Solutions:**
- Challenge — how it was solved
**Impact:**
- Quantified outcome or improvement
**PRs:**
- `repo#number` - description (status)
**Notes:** Links to related notes if any.
Write the update: Use mcp__mcp-obsidian__obsidian_append_content for new entries or read the full file, edit, and rewrite for updates.
Confirm: Tell the user what was logged/updated.