obsidian-tasks
Obsidian Tasks
Manages tasks and PRDs in any Obsidian vault using direct file writes. Obsidian's filesystem watcher picks up changes instantly — no plugin or CLI needed.
Setup
Establish vault context at the start of each session:
- Vault path: absolute path to the vault root — default
~/Documents/Obsidian/<vault-name> - Tasks folder: default
Tasks/ - PRD folder: default
PRD/ - Kanban board: default
Kanban board.md
If not provided, ask the user before proceeding.
Workflows
Create a task
- Determine title, type, priority, git repository and optional jira-ticket/prd from context
- Generate
createdtimestamp:YYYY-MM-DD HH:mm(current date/time) - Write
<vault>/Tasks/<Title>.mdwith frontmatter:
---
title: <title>
type: feature | bug | chore | spike
priority: high | medium | low
blocked-by: []
jira-ticket:
prd:
created: <YYYY-MM-DD HH:mm>
repo:
---
- Add body sections:
## Context,## Task,## Acceptance Criteria,## Notes - Add the task to the Kanban board: read
<vault>/Kanban board.mdand append- [ ] [[<Title>]]as a new item in the## TODOlane - Confirm file path to the user
Create a PRD
Write <vault>/PRD/<Title>.md with:
---
title: <title>
created: <YYYY-MM-DD HH:mm>
status: draft | review | approved
---
Body sections: ## Problem, ## Goals, ## Non-goals, ## Solution, ## Open Questions
Link a task to a PRD
Set prd: "[[PRD Title]]" in the task's frontmatter. Use the exact PRD filename (without .md) as the link target.
Set blocked-by
Set blocked-by as a YAML list in the task's frontmatter:
blocked-by:
- "[[Blocking Task Title]]"
- "[[Another Task]]"
The Kanban plugin renders these as clickable links on cards.
Key rules
- Never use Templater syntax (
<% ... %>) — write final values directly - Filenames = identifiers — wiki-links resolve by filename, so keep titles stable
- Direct writes only — no Obsidian CLI or API required; the vault filesystem is the interface
- Kanban board: always add new tasks to the
## TODOlane inKanban board.md— do not move or reorder existing cards
More from miguelez11/skills
atlassian-cli
Interact with Jira and Confluence from the terminal using the Atlassian CLI (acli). Covers CRUD, listing, searching, commenting, and status transitions on Jira work items, plus Confluence space browsing. Use when the user mentions Jira tickets, ADRs, Confluence spaces, sprint boards, or wants to manage Atlassian work items without leaving the terminal.
13jira-ticket-writer
Write well-structured Jira tickets or improve existing ones. Enforces a consistent template with clear context, problem/request definition, acceptance criteria, and definition of done. Use when user asks to write, create, draft, or improve a Jira ticket, story, bug report, or task — or when a ticket lacks structure or clarity.
8write-a-skill
Add a new agent skill to the MIGUELez11/skills personal GitHub repo. Use when the user wants to create a new workflow, process, or reusable capability and publish it to their skills collection.
6jira-cli
Interact with Jira from the terminal using ankitpokhrel/jira-cli (the `jira` command). Covers issue CRUD, search, sprint management, status transitions, and linking. Use when the user mentions `jira` CLI, wants to create or view Jira issues, list sprints, move tickets, or manage Jira from the terminal without the Atlassian CLI (acli).
5obsidian-prd
Guides the user through a structured PRD creation process via interview, then writes the PRD to an Obsidian vault. Use when user asks to "create a PRD", "add a PRD", "write requirements", "write a spec", or "plan a feature".
3add-skill
Add a new agent skill to the MIGUELez11/skills personal GitHub repo. Use when the user wants to create a new workflow, process, or reusable capability and publish it to their skills collection.
1