By name: task description: "Resolve and operate on Channing's Obsidian vault task notes by frontmatter type. Use when the user references a task note, Jira/GitHub issue tracked by a vault task, asks to inspect or continue task context, or asks to update/capture task state. Routes task_type values such as investigation, implementation, review, and note to the appropriate specialist skill."
Task
Router for vault-backed task work. The task note is the canonical entry point.
Resolve
- Locate the task note under
~/Documents/Notes/Projects/<project>/Tasks/; if the user names a Jira/GitHub issue, find the matching task note first. - Read the task note in full.
- Read linked Jira or GitHub issue if present.
- Read frontmatter and route by
task_type. If missing, treat asnote.
External Data
For investigation tasks, stage long ticket/PR descriptions, comment threads, or diffs into the dossier and reference by path rather than the task note.
Task Note Rules
Do not write unless the user explicitly asks. For Current State, Decision Log, or Open Questions, use task-note-update.
Frontmatter
- Default:
task_type: note - Investigation:
task_type: investigationplusinvestigation_root: ./<same-basename>/README.md
If investigation_root is missing, look for a sibling folder with the same basename as the task note. Ask before creating or moving evidence.
Routes
task_type: investigation- load the task note, linked ticket, andinvestigation_root; then useinvestigation.task_type: implementation- load the task note and linked ticket; then usesoftware-development.task_type: review- load the task note and linked PR/ticket; then usecode-reviewer.task_type: noteor missing - usevaultandtask-note-updateas needed
If a task type is unknown, read the note and ask how to route it.
Investigation Links
For investigation tasks:
- Frontmatter uses
investigation_rootfor machine routing. - Body links to the dossier README and key dossier files near the top link block or under
## Context/## Related. - Dossier details belong to the
investigationskill.