workstream-tracking

Name: workstream-tracking
Author: pariyar07

18stars2forks

How to install workstream-tracking?

pariyar07/ariadne/workstream-tracking

$npx -y skills add pariyar07/ariadne --skill workstream-tracking

Installs into the current project.

Summary

Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Workstream Tracking
2
3	Use this skill when a user wants a visible work board, implementation board, evaluation board, roadmap board, QA board, or dashboard for an Obsidian vault scope.
4
5	This skill creates and improves Markdown-backed workstream state. Kanban and Dataview are view plugins; the durable source of truth remains Markdown tasks, links, and metadata.
6
7	## Plugin Requirements
8
9	Call out plugin requirements before creating plugin-specific views:
10
11	- Obsidian Kanban community plugin: required for drag-and-drop board rendering.
12	- Obsidian Dataview community plugin: required for dynamic dashboard query rendering.
13
14	Do not block the workflow when plugins are missing or unknown. The files still remain readable Markdown. Tell the user that visual Kanban or Dataview rendering needs the relevant plugin enabled in Obsidian.
15
16	## Start
17
18	1. Read the target scope hub, usually `00 Index.md` or `00 ... Index.md`.
19	2. Read the nearest `AGENTS.md` or `CLAUDE.md`.
20	3. Read `Agent/00 Agent Navigation.md` and `Agent/Task Routing Matrix.md` when present.
21	4. Inspect existing `Kanban/`, `Dashboards/`, `Bases/`, and relevant roadmap or implementation notes.
22	5. Decide whether the task is create, audit, improve, or dashboard-only.
23
24	For create, update, file, or add-tracking requests in a multi-scope vault, require a current-turn explicit target before editing. A target is explicit only when the current prompt names a scope, domain, customer, project, or workstream, or the user confirms one after the agent asks. Search hits may identify likely boards, but a single likely match, existing matching cards, prior conversation, current working directory, or active skills are not confirmation. Show the likely target with a short reason and ask before writing.
25
26	Use `ariadne:navigation` when the board requires broader scope routing or structural navigation changes.
27
28	## Board Creation
29
30	Create `Kanban/<Board Name>.md` for recurring workstream state. Use `assets/templates/Workstream Tracking Board.md` as the starting pattern.
31
32	Default columns:
33
34	\| Board type \| Columns \|
35	\| --- \| --- \|
36	\| Implementation \| Backlog, Ready, In Progress, Review / QA, Done \|
37	\| Evaluation or testing \| Backlog, Ready, Running, Evidence Review, Findings, Done \|
38	\| Roadmap \| Ideas, Candidate, Shaping, Ready, Done \|
39	\| QA or validation \| Backlog, Ready, Running, Failed / Follow-up, Passed \|
40
41	Use cards like:
42
43	```markdown
44	- [ ] Define eval rubric [area:: rubric] [priority:: high] [[Relevant Context]]
45	- Cold-agent context: explain enough for a future agent to route and act without asking again.
46	```
47
48	Card rules:
49
50	- Start each card with a concrete verb.
51	- Add `[area:: ...]` and `[priority:: high\|medium\|low]` to every durable card.
52	- Link to the most canonical context note, not every related note.
53	- Add a short child bullet only when cold-agent context materially reduces ambiguity.
54	- Keep completed cards in `Done` unless the user prefers archival cleanup.
55
56	## Dashboard Creation
57
58	Create `Dashboards/<Board Name> Dashboard.md` only when dynamic rollups will help. Use `assets/templates/Workstream Dashboard.md` as the starting pattern.
59
60	Dashboard queries should be narrow:
61
62	- Restrict `FROM` to the relevant `Kanban/` or scope path.
63	- Query tasks when work cards are task lines.
64	- Query notes when tracking source docs, QA records, decisions, or implementation records.
65	- Sort by stable fields such as `priority`, `area`, `file.mtime`, or explicit dates.
66
67	Read `references/dataview-dashboard-patterns.md` before writing non-trivial Dataview queries.
68
69	## Index And Navigation Wiring
70
71	When creating the first board in a scope:
72
73	1. Create or update `Kanban/00 Kanban Index.md`.
74	2. Link all active boards from the index.
75	3. Add `Dashboards/00 Dashboards Index.md` only if dashboards exist.
76	4. Link active dashboards from that index.
77	5. Link the Kanban or Dashboard index from the scope hub when it is part of regular work.
78	6. Add a routing row when future agents should start from the board for a user intent.
79
80	Do not turn `00 Index.md` into a full task list. Link the board index and keep detailed status inside the board.
81
82	## Audit And Improvement
83
84	Use this mode when the user has an existing board or dashboard and asks to verify, clean up, improve, normalize, or make it more useful.
85
86	Inspect:
87
88	- frontmatter has `kanban-plugin: board`, `type: kanban`, status, title, and tags
89	- columns match the workstream lifecycle
90	- tasks have `[area:: ...]` and `[priority:: ...]`
91	- cards link to canonical context notes
92	- child bullets provide useful cold-agent context when needed
93	- `%% kanban:settings` exists for Kanban boards
94	- dashboard Dataview queries use valid source paths and fields
95	- Kanban and Dashboard indexes link the files
96	- scope hub and routing

People who liked this also viewed

6 picks

Type