hk-shift-changelog

Name: hk-shift-changelog
Author: deepklarity

84stars12forks

How to install hk-shift-changelog?

deepklarity/harness-kit/hk-shift-changelog

$npx -y skills add deepklarity/harness-kit --skill hk-shift-changelog

Installs into the current project.

Summary

Create and maintain a shift-handover HTML changelog artifact — a page the returning human reads in two minutes to know everything that happened while they were away. Generic across projects. Use when working autonomously for an away user, when asked for a changelog/progress page/

Files · 1

View on GitHub

SKILL.md

1	# Shift-handover changelog (project-agnostic)
2
3	One living HTML page, rewritten (never appended) at every meaningful
4	transition, redeployed to the SAME artifact URL every time. The reader is
5	a teammate back from sleep or a weekend: they want the state of the world,
6	not a log.
7
8	## Where it lives
9
10	- File: one stable path in the repo (e.g. `docs/<area>/changelog.html`),
11	committed, so any future session can find and redeploy it.
12	- URL: record the artifact URL in the project's durable operator notes
13	(state/RESUME file) the first time you publish. Every later publish
14	passes that `url` — never mint a second artifact for the same duty.
15	- Favicon: pick one emoji the first time; never change it (users find the
16	tab by icon).
17
18	## Structure (top-down by how fast the reader wants out)
19
20	1. Header — project + "shift handover", a stamp saying what period it
21	covers (relative, not raw timestamps).
22	2. TL;DR box — 3-5 sentences: what changed, what's running, whether
23	anything is blocked on the reader. If they read nothing else, this
24	suffices.
25	3. What happened, in order — timeline entries: a short label (wave
26	close / incident / directive / decision), a bold headline, 1-3
27	sentences, and a status pill (DONE / RUNNING / VERIFIED / WAITING).
28	Every user directive gets its own entry so they can verify they were
29	understood.
30	4. Scoreboard / metrics — whatever the project tracks (bucket scores,
31	suites, costs), as a table with movement + evidence, never bare deltas.
32	5. Waiting on you — a numbered list of decisions only the human can
33	make. This section earns the page its keep; keep it brutally current.
34	6. Footer — "living document, rewritten each transition" + where the
35	ground truth lives.
36
37	## Design rules
38
39	Load the `artifact-design` skill before first authoring. Beyond it:
40	- Utilitarian treatment: real hierarchy, quiet type, one accent; both
41	themes via CSS tokens (`prefers-color-scheme` + `data-theme` overrides).
42	- Bind background AND text color to the SAME token set on `html, body`
43	with `!important`. The artifact shell may force its own body background;
44	if your ink tokens go dark while its ground stays light, the page is
45	unreadable (seen live). Background and ink must move together or not at
46	all.
47	- Self-contained (CSP): no external fonts/scripts; system font stacks.
48	- Tables wrapped in `overflow-x:auto`; digits get `tabular-nums`.
49	- Plain language throughout; no ids or jargon the reader must decode; name
50	things by what they mean, cite ids only as secondary `mono` detail.
51
52	## Cadence
53
54	Rewrite + redeploy at: phase/wave boundaries, incidents and their fixes,
55	user directives received while away, score/metric movements, and anything
56	that adds to "Waiting on you". Batch small transitions; never let the page
57	drift more than ~30 min behind a meaningful one. Keep the file and the
58	deployed artifact in lockstep — commit the file in the same breath.

People who liked this also viewed

6 picks

Type

hk-shift-changelog

84stars12forks

View on GitHub

How to install hk-shift-changelog?

deepklarity/harness-kit/hk-shift-changelog

$npx -y skills add deepklarity/harness-kit --skill hk-shift-changelog

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Shift-handover changelog (project-agnostic)
2
3	One living HTML page, rewritten (never appended) at every meaningful
4	transition, redeployed to the SAME artifact URL every time. The reader is
5	a teammate back from sleep or a weekend: they want the state of the world,
6	not a log.
7
8	## Where it lives
9
10	- File: one stable path in the repo (e.g. `docs/<area>/changelog.html`),
11	committed, so any future session can find and redeploy it.
12	- URL: record the artifact URL in the project's durable operator notes
13	(state/RESUME file) the first time you publish. Every later publish
14	passes that `url` — never mint a second artifact for the same duty.
15	- Favicon: pick one emoji the first time; never change it (users find the
16	tab by icon).
17
18	## Structure (top-down by how fast the reader wants out)
19
20	1. Header — project + "shift handover", a stamp saying what period it
21	covers (relative, not raw timestamps).
22	2. TL;DR box — 3-5 sentences: what changed, what's running, whether
23	anything is blocked on the reader. If they read nothing else, this
24	suffices.
25	3. What happened, in order — timeline entries: a short label (wave
26	close / incident / directive / decision), a bold headline, 1-3
27	sentences, and a status pill (DONE / RUNNING / VERIFIED / WAITING).
28	Every user directive gets its own entry so they can verify they were
29	understood.
30	4. Scoreboard / metrics — whatever the project tracks (bucket scores,
31	suites, costs), as a table with movement + evidence, never bare deltas.
32	5. Waiting on you — a numbered list of decisions only the human can
33	make. This section earns the page its keep; keep it brutally current.
34	6. Footer — "living document, rewritten each transition" + where the
35	ground truth lives.
36
37	## Design rules
38
39	Load the `artifact-design` skill before first authoring. Beyond it:
40	- Utilitarian treatment: real hierarchy, quiet type, one accent; both
41	themes via CSS tokens (`prefers-color-scheme` + `data-theme` overrides).
42	- Bind background AND text color to the SAME token set on `html, body`
43	with `!important`. The artifact shell may force its own body background;
44	if your ink tokens go dark while its ground stays light, the page is
45	unreadable (seen live). Background and ink must move together or not at
46	all.
47	- Self-contained (CSP): no external fonts/scripts; system font stacks.
48	- Tables wrapped in `overflow-x:auto`; digits get `tabular-nums`.
49	- Plain language throughout; no ids or jargon the reader must decode; name
50	things by what they mean, cite ids only as secondary `mono` detail.
51
52	## Cadence
53
54	Rewrite + redeploy at: phase/wave boundaries, incidents and their fixes,
55	user directives received while away, score/metric movements, and anything
56	that adds to "Waiting on you". Batch small transitions; never let the page
57	drift more than ~30 min behind a meaningful one. Keep the file and the
58	deployed artifact in lockstep — commit the file in the same breath.

People who liked this also viewed

6 picks

Type