From stafraen-heilsa
Stafræn Heilsa project hub — three modes: (1) KICKOFF: invoke with /kickofftool, "new project", or when dropping spec documents. Runs structured intake per Hönnunarhandbók 4-phase UCD process and creates the full Notion hub. (2) DESIGN SPRINT: invoke when brainstorming UI/UX layouts — "brainstorm the design", "show me options", "mock this up", "what could this look like". Requires superpowers + frontend-design plugins; falls back to text brainstorm if missing. (3) ARTIFACT PUSH: after any session producing plans, decisions, or specs — push to Notion. Offer proactively at session end. Requires Notion MCP for all modes. Always use this skill for Stafræn Heilsa / Embætti landlæknis project work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/stafraen-heilsa:nytt-verkefniThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill has three modes that share the same Notion project structure:
This skill has three modes that share the same Notion project structure:
Both modes follow the Stafræn Heilsa Hönnunarhandbók (Edition 2, April 2026), which defines a mandatory 4-phase User-Centered Design process for all digital health solutions in Iceland.
All projects follow four phases in order. Never start a later phase before completing the prior one:
| Phase | Icelandic name | Purpose |
|---|---|---|
| 1 | Skilgreining (Define) | Purpose, goals, measurable effects, user groups, stakeholders |
| 2 | Greining (Discover) | Needs analysis — processes, roles, tasks, requirements |
| 3 | Hugmyndir (Innovate) | Solution concepts, wireframes, user stories list |
| 4 | Hönnun og þróun (Develop) | Full design + development, user story by story |
Each phase has:
Every project uses exactly this structure — no variation, so all projects feel familiar:
📁 [Project Name]
├── 📋 Overview — status, current phase, goals, team, timeline, repo
├── 📐 Skilgreining — Phase 1 artifacts (purpose, goals, effects, stakeholders)
├── 🔍 Greining — Phase 2 artifacts (process descriptions, roles, needs)
├── 💡 Hugmyndir — Phase 3 artifacts (concepts, wireframes, user stories)
├── 🛠️ Hönnun og þróun — Phase 4 artifacts (user story specs, UI, test results)
├── ✅ Tékklistar — Checklists for each phase, tracked here
├── 📦 Backlog — Prioritized work items
└── 🗒️ Notes — Reference links, misc context, meeting notes
Trigger when:
/kickofftool or similarIf files are provided, read them before asking anything. Extract every answerable fact:
| Hönnunarhandbók fact | Look for in docs |
|---|---|
| Project name | Title, heading, email subject |
| Tilgangur (purpose) | Executive summary, problem statement, "af hverju" |
| Markmið (measurable goals) | Goals section, KPIs, success metrics |
| Áhrif (measurable effects) | Expected outcomes, before/after comparisons |
| Notendahópar (direct users) | User personas, "designed for", audience |
| Hagaðilar (stakeholders) | Sign-offs, distribution lists, sponsors |
| Existing processes | Workflow docs, process diagrams |
| Tech stack / platform | Architecture sections, technical requirements |
| Timeline / milestones | Gantt charts, launch dates, contract dates |
| Known constraints | Compliance, budget, "out of scope", WCAG requirements |
| Existing knowledge / systems | "Þekkingarkortagning" — prior art, legacy systems |
| Contact list for research | Named contacts for user interviews |
After reading, internally compile "Known facts" and present them to the user for confirmation before asking follow-up questions.
Present known facts, then ask only what's missing. Do it conversationally in rounds.
Opening message format:
Ég fann [N] atriði í skjölunum. Látum mig staðfesta það sem ég veit og fylla síðan í eyðurnar.
**Úr skjölunum:**
- Heiti verkefnis: [X]
- Tilgangur: [X]
- [etc.]
**Nokkur atriði sem ég þarf enn:**
1. [Question]
2. [Question]
If no documents were provided, ask in 3 rounds (wait for answers between rounds):
Round 1 — Core (Skilgreining, section 3.2):
Round 2 — Users & stakeholders:
Round 3 — Context & constraints:
After gathering answers, show a Project Summary and ask for confirmation before touching Notion.
📁 [Project Name]# [Project Name] — Overview
**Staða (Status):** Virkt / Í bið / Lokið
**Fasi (Phase):** Skilgreining / Greining / Hugmyndir / Hönnun og þróun
**Repo:** [link or TBD]
**Síðast uppfært:** [date]
---
## Tilgangur
[One paragraph — why this solution exists, for whom]
## Markmið og áhrif
| Markmið | Mælikvarði |
|---------|-----------|
| [goal] | [metric] |
**Væntanleg áhrif:**
- [effect] — mælt með [metric]
## Teymi og hagaðilar
| Hlutverk | Nafn |
|----------|------|
| Talsmаður notenda | [name] |
| Ábyrgðaraðili | [name] |
| [other roles] | [name] |
## Notendahópar
| Hlutverk | Lýsing |
|----------|--------|
| [role] | [description] |
## Tímalína
| Áfangi | Dagsetning |
|--------|-----------|
| Lok Skilgreiningar | [date] |
| Lok Greiningar | [date] |
| Lok Hugmynda | [date] |
| Verklok | [date] |
## Þekktir takmarkanir
[List, or "Engar þekktar"]
## Lykiltengar síður
- Skilgreining: [link]
- Tékklistar: [link]
- Backlog: [link]
# Skilgreining — [Project Name]
> Verkáfangi 1 samkvæmt Hönnunarhandbók Stafrænar Heilsu
## Tilgangslýsing
[Clear statement of purpose]
## Markmálslýsing
[Measurable goals]
## Áhrifslýsing
[Measurable effects — what changes after launch]
## Notendahópar
[List of direct user roles]
## Hagaðilar
[List of stakeholders who are not direct users]
## Þekkingarkortagning
[Summary of existing knowledge, processes, legacy systems, prior research]
## Tengiliðalisti fyrir rannsókn
[Contacts for user interviews and observations in Phase 2]
Checklist for each phase tracked here. Use Notion checkboxes. Items marked (*) require user testing evidence.
# Tékklistar — [Project Name]
## Verkáfangi 1: Skilgreining ✅/🔄
- [ ] Tilgangur stafrænu lausnarinnar er skýr
- [ ] Markmið stafrænu lausnarinnar er skilgreint og mælanlegt
- [ ] Áhrif stafrænu lausnarinnar eru skilgreind og mælanleg
- [ ] Notendahópar eru skilgreindir
- [ ] Hagaðilar eru skilgreindir
- [ ] Þekking á verkefninu er kortlögð
- [ ] Núverandi ferlar, lausnir og eyðublöð eru til staðar
- [ ] Skilgreindur tengiliður til að skipuleggja rannsóknarviðburði
- [ ] Skilgreining kynnt viðeigandi aðilum (verktaka, þróunarteymi)
## Verkáfangi 2: Greining 🔄/⏳
- [ ] Talað hefur verið við raunverulega notendur um þarfir og væntingar
- [ ] Aðstæður notenda hafa verið kannaðar eða lýst af notendum sjálfum
- [ ] Til er lýsing á ferlinu sem lausnin á að styðja
- [ ] Til eru hlutverkalýsingar á notendum
- [ ] Til eru verkefnalýsingar (scenarios) fyrir hvert hlutverk
- [ ] Þarfir og væntingar notenda eru skilgreindar og forgangsraðaðar
- [ ] Þarfir og væntingar hagaðila eru skilgreindar og forgangsraðaðar
- [ ] Uppfærður tengiliðalisti fyrir notendaprófarnar
- [ ] Niðurstöður greiningar kynntar þróunarlið
## Verkáfangi 3: Hugmyndir ⏳
- [ ] Þverfagleg teymi tóku fram hugmyndir að lausnum
- [ ] Fleiri tillögur að lausnum teknar fram og bestu valdar
- [ ] Valdar lausnir styðja tilgang og markmið
- [ ] Valdar lausnir styðja skilgreind áhrif
- [ ] Valdar lausnir styðja ferla og hlutverk
- [ ] (*) Valdar lausnir styðja við lausn þeirra verkefna sem eru skilgreind
- [ ] (*) Valdar lausnir mæta þörfum og væntingum notenda
- [ ] (*) Notandi hefur góða yfirsýn og þarf ekki að opna margar skjámyndir
- [ ] (*) Notast er við orðalag sem notandi þekkir
- [ ] (*) Tekið er tillit til aðstæðna og aðgengis notenda
- [ ] Lausnir (concepts) eru notendaprófaðar af lykilnotendum
- [ ] Notendassögur sem lausnin á að styðja eru listaðar upp og forgangsraðaðar
## Verkáfangi 4: Hönnun og þróun ⏳
- [ ] Þróunarteymi fékk kynningu á grófu hönnun
- [ ] Notendassögur eru forgangsraðaðar út frá þörfum og ferli notenda
- [ ] Hverja notendassögu er lýst skv. skilgreindu sniði
- [ ] (*) Hönnun fylgir 10 Usability Heuristics (Jakob Nielsen)
- [ ] (*) Leiðarkerfi er skilvirkt og stutt í allar helstu aðgerðir
- [ ] (*) Notandi hefur alltaf góða yfirsýn
- [ ] (*) Notast er við einfalt orðalag sem fylgir orðanotkun notanda
- [ ] (*) Mikilvægar/brýnar upplýsingar eru gerðar sýnilegar
- [ ] (*) Hönnun fylgir WCAG 2.2 AA staðli
- [ ] (*) Allir hnappar hafa lýsandi texta, treysta ekki eingöngu á tákn
- [ ] Notendaprófarnar skipulagðar og framkvæmdar í hverjum spretti eða með reglulegu millibili
- [ ] Þróunarteymi undirbiður röni en notandi framkvæmir aðgerðirnar
This mode is for when design/UI decisions need to be made visually — not described in text.
It combines superpowers:brainstorming (which drives the Visual Companion server) with
frontend-design (which generates the mockup HTML), and saves all decisions to Notion's
💡 Hugmyndir section.
Trigger when:
Do NOT use this mode for:
Step 0 — Check prerequisites
Before starting, check whether superpowers:brainstorming and frontend-design are available
in the current session's skill list.
If either is missing, do not attempt the Visual Companion flow. Instead:
superpowers and frontend-design
plugins installed. I can still run a text-based design brainstorm now, and you can get the
full visual experience once those are installed."If both are available, continue with the full visual flow below.
Step 1 — Invoke superpowers:brainstorming
The brainstorming skill drives the whole visual session. It will:
scripts/start-server.sh --project-dir <project-dir>
with run_in_background: true on Windowsscreen_dir, read user clicks from state_dir/eventsYour job during this step: make sure the brainstorming is grounded in the Hönnunarhandbók. Specifically, hold these in context throughout:
Step 2 — Generate mockups with frontend-design quality
When writing HTML for the Visual Companion, use frontend-design skill principles:
cards or options classessplit class for direct side-by-side comparison of two layoutsStep 3 — Capture decisions after the sprint
When the brainstorming session ends and design direction is agreed, save a summary to Notion:
Route to: 💡 Hugmyndir → new sub-page titled [Topic] — Gróf hönnun [date]
# [Topic] — Gróf hönnun
> Búið til: [date] | Heimild: Design sprint með Visual Companion
> Samantekt: [one sentence — the key design direction chosen]
---
## Valið hönnunarsnið
[Description of the chosen direction — what was decided and why]
## Skjáskipulag (e. Information architecture)
[Key screens, navigation structure, what's on each screen]
## Notendassögur sem þetta styður
[List of user stories this design serves — from Phase 1 / Phase 2]
## Hönnunarákvarðanir sem teknar voru
| Spurning | Ákvörðun | Rökstuðningur |
|----------|----------|--------------|
| [design question] | [chosen option] | [why] |
## Aðgengi (WCAG)
[Accessibility decisions made during the sprint — contrast choices, navigation, etc.]
## Útilokuð valkostur
[Options that were explored but rejected — and why. This prevents re-litigating decisions.]
## Næstu skref
- [ ] [next design/development action]
Also update the project Overview page: set Phase to "Hugmyndir" if not already set.
After saving to Notion, check which Hugmyndir tékklistar items the sprint addressed and flag them as ready for user testing (they cannot be marked complete without testing):
Flag these as "Tilbúið til notendaprófa" (ready for user testing) — not checked off yet.
Route session output to the right sub-page based on content type:
| Session type | Route to |
|---|---|
superpowers:writing-plans output | 🛠️ Hönnun og þróun → new sub-page |
superpowers:brainstorming output | 💡 Hugmyndir → new sub-page |
| Architectural / technical decision | 🗒️ Notes → append to Decisions section |
| User research findings | 🔍 Greining → new sub-page |
| User story specifications | 🛠️ Hönnun og þróun → new sub-page |
| Phase checklist update | ✅ Tékklistar → update checkboxes |
| Backlog items | 📦 Backlog → append |
| Phase / status change | 📋 Overview → update Phase and Staða fields |
| Code/security review | 🛠️ Hönnun og þróun or 🗒️ Notes |
| Misc reference / links | 🗒️ Notes |
When in doubt, use 🗒️ Notes.
# [Title]
> Búið til: [date] | Heimild: Claude [skill-name] session
> Samantekt: [one sentence]
---
[content]
At the end of any session that produced plans, decisions, user research, specs, or significant findings — if this skill hasn't already run — offer one line:
"Want me to save this to the [project name] Notion hub?"
One offer per session. Don't repeat it.
Two full handbooks are available as reference files. Load them when relevant — do not load both at once unless comparing them directly.
references/honnunarhandbok.md — Hönnunarhandbók Stafrænar Heilsu (Edition 2, April 2026)Load when:
Key sections:
references/throdunarhandbok.md — Þróunarhandbók Stafrænar Heilsu (Edition 4, April 2026)Load when:
Key sections (by chapter):
Important: Þróunarhandbók requirements marked SKAL are binding in contracts. When a project's proposed approach conflicts with a SKAL item, flag this explicitly and reference the undanþáguferill (exception process) described in the handbook appendix.
references/throdunarhandbok-vidaukar.md — Þróunarhandbók Viðaukar (Edition 4, April 2026)Detailed technical appendices — separate document, 58 pages. Load this instead of or alongside the main Þróunarhandbók when deep technical specifics are needed.
Load when:
Key appendices:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
npx claudepluginhub mrh-landlaeknir/claude-plugin --plugin stafraen-heilsa