dot_agents/exact_skills/tracking-tasks/SKILL.md
Use when starting multi-step work, resuming an existing task, switching direction mid-task, wrapping up, or capturing cross-session task context in Obsidian.
npx skillsauth add h3y6e/dotfiles tracking-tasksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
~/ghq/github.com/h3y6e/log — if missing, ghq get log.
Path: task/YYYY-MM-DD-<slug>.md. Frontmatter: title, status (backlog→todo→in-progress→done/canceled). Sections: Goal, DoD (checklist), Research, Notes.
obsidian search:context or direct rg under the log vault, then read the file directly.in-progress.Make the Obsidian graph useful with [[wikilinks]]; do not treat notes as isolated logs.
Triggers are session-wide — even without a task note, even on single-response tasks. Write at the moment of discovery, not batched at the end.
Path: obsidian daily:path vault=log → daily/YYYY-MM-DD.md. If CLI fails, use ~/ghq/github.com/h3y6e/log/daily/YYYY-MM-DD.md.
Triggers — TIL, workarounds, cross-cutting decisions, env/tooling issues, useful links, recurring patterns.
If a finding is both task-relevant and cross-cutting, log task impact in the task note and the broader concern in the daily note separately.
The CLI is unstable. If any command errors, immediately fall back to direct file editing — do not retry or debug. Prefer direct editing over obsidian append for backticks or shell-sensitive content.
obsidian daily:path vault=log → get today's date (use this, not date command)obsidian create vault=log path="task/YYYY-MM-DD-slug.md" template=task[[wikilinks]] so graph/backlinks connect the task to related workobsidian property:set vault=log path="task/..." name=status value=in-progressobsidian task vault=log path="task/..." line=N toggleobsidian property:set vault=log path="task/..." name=status value=donetools
Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.
tools
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
testing
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
development
Use when making code changes in a git repo, switching branches, or when asked to `push`, `commit`, `pr`, or manage branches. Use before starting implementation to confirm you're on the right branch.