feat(work): add sub-item wiki-links and external tracker link formats#143
feat(work): add sub-item wiki-links and external tracker link formats#143
Conversation
- Add Sub-item wiki-links section: [[wiki-link]] in checklists, create .md when starting work - Add External Tracker Links section: compact jira:/github: formats for frontmatter and inline - Fix jira frontmatter format to use compact atlassian-org/TICKET-ID Mirrors changes in treasure-data/tdx#2062. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the Work skill documentation to standardize how workspace items reference sub-tasks and external trackers (Jira/GitHub), aligning with the companion system-prompt changes.
Changes:
- Updates the
jirafrontmatter example to a compact<org>/<TICKET-ID>format. - Adds guidance for representing sub-tasks as wiki-links inside checklist items.
- Adds a new section documenting compact external tracker link formats for both frontmatter and inline references.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - [ ] [[2026-03-26-add-auth-refresh]] — Token refresh logic | ||
| - [ ] [[2026-03-26-update-api-docs]] — Update REST docs | ||
| - [x] [[2026-03-26-fix-session-expiry]] — Session timeout fix |
There was a problem hiding this comment.
The checklist example uses date-prefixed wiki-links like [[2026-03-26-add-auth-refresh]], but earlier in this doc wiki-links are described/resolved using the item slug (e.g., [[fix-login-bug]]) with matching via *-{slug}.md. Using the full filename stem (including date) here creates an inconsistent convention and can make links less stable if the date changes. Consider updating the examples to use slug-only links (e.g., [[add-auth-refresh]]), or explicitly clarify that sub-item wiki-links should target the full filename stem and adjust the earlier wiki-link guidance accordingly.
| - [ ] [[2026-03-26-add-auth-refresh]] — Token refresh logic | |
| - [ ] [[2026-03-26-update-api-docs]] — Update REST docs | |
| - [x] [[2026-03-26-fix-session-expiry]] — Session timeout fix | |
| - [ ] [[add-auth-refresh]] — Token refresh logic | |
| - [ ] [[update-api-docs]] — Update REST docs | |
| - [x] [[fix-session-expiry]] — Session timeout fix |
| **Frontmatter fields** (field name provides the type): | ||
|
|
||
| ```yaml | ||
| jira: <atlassian-org>/<TICKET-ID> # e.g., acme-corp/PROJ-1234 |
There was a problem hiding this comment.
In the frontmatter format example, the placeholder jira: <atlassian-org>/<TICKET-ID> reads like atlassian-org is a literal value, but the inline example uses acme-corp/PROJ-1234. To avoid confusion, consider renaming the placeholder to something like <jira-org> (or <org>) and keep examples consistent with that naming.
| jira: <atlassian-org>/<TICKET-ID> # e.g., acme-corp/PROJ-1234 | |
| jira: <jira-org>/<TICKET-ID> # e.g., acme-corp/PROJ-1234 |
Summary
[[wiki-link]]in checklists, create.mdfile when starting work on a sub-taskjira:/github:formats for both frontmatter fields and inline markdown referencesjirafrontmatter example to use compactatlassian-org/TICKET-IDformat instead of full URLCompanion to treasure-data/tdx#2062 (system prompt side).
Test plan
🤖 Generated with Claude Code