From studio-skills
Manages Treasure Studio workspace documents including items, goals, notes, guides, and references via markdown file operations. Creates, updates, lists, tracks status/priority, and links to GitHub/Jira.
npx claudepluginhub treasure-data/td-skills --plugin treasure-work-skillsThis skill uses the workspace's default tool permissions.
Manage workspace documents (items, goals, notes, guides, references) using file operations. All state lives in markdown files with YAML frontmatter.
Manages tasks-plans/ workspace by adding actionable items to backlog, ideas for exploration, or dated references. Organizes files by topic into subfolders, processes queued work via subcommands.
Creates, lists, and updates persistent work items to track tasks, priorities, and statuses across sessions, mitigating context rot in long-running Claude conversations.
Share bugs, ideas, or general feedback.
Manage workspace documents (items, goals, notes, guides, references) using file operations. All state lives in markdown files with YAML frontmatter.
Workspaces are stored under ~/tdx/work/:
~/tdx/work/local/{name}/ (default workspace: ~/tdx/work/local/default/)~/tdx/work/github/{owner}/{repo}/Each workspace root contains a tdx.json config file. The current working directory is typically set to the active workspace.
| Folder | Kind | Filename Pattern |
|---|---|---|
goals/ | goal | {slug}.md (no date prefix) |
items/ | item | YYYY-MM-DD-{slug}.md |
schedules/ | schedule | {task-name}/ (subdirectory with TASK.md + schedule.yaml) |
guides/ | guide | YYYY-MM-DD-{slug}.md |
notes/ | note | YYYY-MM-DD-{slug}.md |
notes/weekly/ | weekly note | YYYY-WNN.md |
references/ | reference | YYYY-MM-DD-{slug}.md |
Every document has YAML frontmatter:
---
title: My Work Item
status: todo # items/goals: backlog|todo|planning|design_review|in_progress|review|done|void
# guides: proposed|accepted|deprecated|superseded
tags: [feature, auth]
priority: medium # critical|high|medium|low (items/goals only)
assignee: Name # items/goals only
due: 2026-04-01 # items/goals only
github: owner/repo#123 # link to GitHub issue or PR (items/goals only)
jira: atlassian-org/PROJ-456 # link to Jira ticket (items/goals only)
created: 2026-03-23
updated: 2026-03-23
---
Guides also support description: — a one-line summary shown in the guide index and injected into agent context for accepted guides.
Notes and references only need title, tags, created. References add source: URL.
Slugify the title: lowercase, replace non-alphanumeric with hyphens, trim edges, max 60 chars.
fix-login-bugtitle, created (today), status (default: todo for items, proposed for guides)Item example:
---
title: Fix Login Bug
status: todo
tags: [bug, auth]
priority: high
created: 2026-03-23
---
Login fails when password contains special characters.
→ Write to items/2026-03-23-fix-login-bug.md
Goal example:
---
title: Auth Redesign
status: todo
tags: [q2, security]
created: 2026-03-23
---
Redesign the authentication system.
## Linked Items
- [[fix-login-bug|Fix Login Bug]]
→ Write to goals/auth-redesign.md
Use wiki-links for bidirectional linking:
- [[item-slug|Display Title]]Part of [[goal-slug]].Wiki-link format: [[slug]] or [[slug|Display Text]]
Read the file, update the status field in frontmatter, set updated to today.
Use Glob to find files, Read to inspect frontmatter:
Glob("items/*.md")Glob("goals/*.md")status: in_progress in the target folderUse Grep to search across notes, guides, and references:
Grep(pattern, path: "notes/") or across all knowledge foldersGrep("tags:.*keyword", glob: "{notes,guides,references}/**/*.md")[[slug]] or [[slug|Display Text]]items/*{slug}.md)status fieldFind the first linked item in a goal that isn't done or void.
When resolving [[slug]]:
Glob("{goals,items,guides,notes,references}/{slug}.md") or Glob("{goals,items,guides,notes,references}/*-{slug}.md")For backlinks (who links to this document): Grep("\\[\\[{slug}", glob: "**/*.md")
When committing workspace changes, use this message format:
work: move "Title" old_status → new_statuswork: create "Title"work: update "Title"When an item has sub-tasks, use [[wiki-link]] in checklists — even if the target page doesn't exist yet:
- [ ] [[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
When starting work on a sub-task, create the actual .md file in items/ so it becomes a trackable item with its own status and links.
Frontmatter fields (field name provides the type):
jira: <atlassian-org>/<TICKET-ID> # e.g., acme-corp/PROJ-1234
github: <owner>/<repo>#<number> # e.g., acme-corp/my-app#456
Inline references in markdown body (prefix with jira: or github:):
- [x] Auth token refresh — jira:acme-corp/PROJ-1234
- [ ] Update API docs — github:acme-corp/my-app#789
Grep(pattern, path: "guides/")Workspace schedules live in schedules/{task-name}/ with TASK.md + schedule.yaml.
Built-in schedules (weekly-review, synthesize-knowledge, stale-item-cleanup) are auto-created.
To create a new workspace schedule:
schedules/{task-name}/TASK.md and schedules/{task-name}/schedule.yamlschedule_reload to register the taskschedule_run to test, then schedule_enable to activateWorkspace-only schedule.yaml fields:
goal: {slug} — scope to a goal's linked itemsskill: {name} — invoke a workspace skill (different from skills which lists capability packs)output.note: true — auto-create a Note from resultsoutput.note_tags: [tag1, tag2] — tags added to the auto-created Note