Task

---
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, experiment, and note to the appropriate specialist skill."
---

# Task

Router for vault-backed task work. The task note is the canonical entry point.

## Resolve

1. Locate the task note under `~/Documents/Notes/Projects/<project>/Tasks/`; if the user names a Jira/GitHub issue, find the matching task note first.
2. Read the task note in full, then the notes it links to, one hop deep.
3. Read the linked Jira, GitHub, or Linear ticket yourself rather than asking the user to summarise it.
4. Read frontmatter and route by `task-type` (a few legacy notes use `task_type`; treat it the same). If missing, treat as `note`.
5. When resuming work and the note has a `## Next Session` block, take it as the starting instruction. If its date is older than Current State's `*Updated:*`, it is stale — ignore it and say so.

## 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`. If any of those three sections is missing, offer to add it.

Whatever the section — including hand-written ones like `Design`, `Hypotheses`, or `Context` — write for a reader scanning the note: prefer real markdown lists over dense prose, keep sentences short, give each distinct fact its own bullet, and never use inline `(1)… (2)…` / `(a)… (b)…` pseudo-lists where a real list belongs.

## Frontmatter

- Default: `task-type: note`
- Investigation: `task-type: investigation` plus `investigation_root: ./<same-basename>/README.md`
- Experiment: `task-type: experiment` plus a `research:` wikilink to its research note

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, and `investigation_root`; then use `investigation`.
- `task-type: implementation` - load the task note and linked ticket; then use `software-development`.
- `task-type: review` - load the task note and linked PR/ticket; then run the host's native code review as `fix-loop` describes it for this host, reporting only. Use `fix-loop` itself when the task also asks for fixes.
- `task-type: experiment` - load the task note and its linked research note; use `task-note-update` for capture and `obsidian-research-maintainer` for roll-up.
- `task-type: note` or missing - use `vault` and `task-note-update` as needed

If a task type is unknown, read the note and ask how to route it.

## Investigation Links

For investigation tasks:

- Frontmatter uses `investigation_root` for 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 `investigation` skill.