wiki-tasklisted

# wiki-task Read these files fully before proceeding: - `skills/_shared/task-rules.md` - `skills/_shared/vault-conventions.md` Then attempt to read `.obsidian/copilot/tag-index.md` (at vault root). If the file does not exist, note it and continue — tags will be omitted from tasks. See the "If `tag-index.md` does not exist" section in `task-rules.md`. Invoke with: `/wiki-task <description>` --- ## Step 1 — Resolve VAULT_PATH Vault path: `~/obsidian_vault` by default; set `VAULT_PATH` to override. WSL users with a Windows-side vault must set `VAULT_PATH` explicitly (e.g. `/mnt/c/Users/<name>/obsidian_vault`). All file paths below are relative to the vault root. --- ## Step 2 — Parse the prompt Analyse the natural-language `<description>` and extract every field you can. Do not ask follow-up questions for fields that are simply absent — leave them at their defaults. Only ask the user when the prompt is genuinely ambiguous (e.g., two plausible target projects). ### 2.1 — Description text The core task description. Strip out metadata you extract into other fields (dates, priority words, effort hints) so the description reads cleanly. ### 2.2 — Effort estimate Map effort hints to Fibonacci values using the scale in `task-rules.md`. Heuristics: - Explicit numbers or words: "5 min" → `[0]`, "quick" → `[0]`–`[1]`, "half a day" → `[3]`, "a few days" → `[5]`, "a week" → `[8]`. - Action verbs: "review" / "approve" / "check" → lean `[0]`–`[1]`; "implement" / "build" / "m