Stop-hooken var type `prompt`: en prompt-Stop-hook sendes til modellen
hver gang økten stopper, og enhver ikke-tom output tolkes som feedback →
agenten re-invokeres → stopper igjen → loop. «Skip entirely if no OKR
work»-grenen kunne aldri bli helt taus (modellen forklarer at den
skipper = ikke-tom output), så den looper hver økt uten OKR-arbeid.
Observert i praksis: 6+ runder før harness flagget «Stop hook error».
Funksjonen var dessuten svak: en blind prosa-nudge som ikke kan
verifisere om arbeid er lagret, og som peker på integrasjoner som knapt
er wiret (Oboard: ingen; Linear: valgfri MCP). Kontinuitet er allerede
dekket av PreCompact-hooken (bevarer arbeid-i-progresjon) + STATE.md.
Fjernet framfor å konvertere til command-hook (over-engineering uten
reell sync-sjekk). Revurderes hvis ekte ekstern-tracker-integrasjon
lander (Fase 3).
Versjonssync → 1.3.2: plugin.json, README-badge, SKILL.md, og rettet
stale CLAUDE.md-header (v1.3.0 → v1.3.2; Fase 0 bommet på denne).
Fjernet Stop-raden fra CLAUDE.md Hooks-tabell.
Fase 1-prosaen innførte den korrekte moderne forkortelsen DFØ i
dfo-okr-mapping.md, mens resten av fila (+ README, SKILL) brukte den
upresise legacy-formen DFO. Samme etat staves dermed to måter — en
konsistens-sprekk en DFØ/Riksrevisjon-leser (pluginets målgruppe) fanger.
Harmonisert hele pluginen mot DFØ (offisiell form, Direktoratet for
forvaltning og økonomistyring):
- dfo-okr-mapping.md: 20 tokens (14 ordgrense + 6 genitiv «DFOs»→«DFØs»)
- README.md: 2 tokens
- SKILL.md: 1 token
dfo.no-URLene er urørt (faktisk domene, ikke forkortelsen). Filnavnet
dfo-okr-mapping.md beholdes (ASCII-slug; rename ville brutt referanser).
Ingen versjonsbump (Fase 1-disiplin — filene forblir 1.3.1).
Løser review.md MAJOR-funn a1f3c9e2 (PLAN_EXECUTE_DRIFT,
verdict WARN → resolved).
Pilot review for a marketplace-wide review method. config-audit v5.4.0 (posture A,
plugin-health 0) + llm-security (A-, 0 critical/high/medium) + structure + version.
Verdict: strong, low-risk plugin. 2 Low nits (assert cycle-ID before rm in oppsett.md:457;
SECURITY.md:57 key-storage guidance). Read-only review; this file is the only artifact.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ter3E2JSi1Khgmuf2kady8
Pre-trekexecute snapshot of in-progress CLAUDE.md/SKILL.md edits and
extracted docs/ files. Captured as one commit so /trekexecute claude-design
can run against a clean working tree.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Standardize named-markdown-link guidance across all plugins so file://
references render as independently clickable links in terminals like
Ghostty (bare file:// URLs only make the first clickable).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Establish a single governance document at marketplace root and copy
it into each of the 9 plugins so every plugin folder remains 100%
self-contained. Replace the inconsistent provocative blurb across
all READMEs with a uniform fork-and-own paragraph that links to
the local GOVERNANCE.md.
[skip-docs]
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Transparency: all code in this marketplace is produced by Claude Code
through dialog-driven development. Root README gets a full disclosure
section; each plugin README gets a one-line disclosure linking back to
the marketplace section.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Shift focus from tildelingsbrev-specific to general strategy transformation.
More motivating, explains what and why for leaders/advisors, not developers.
Updated marketplace root README section to match.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Lead with strategy → OKR, not tildelingsbrev → OKR
- Tildelingsbrev repositioned as early analysis tool for leaders
- Broaden tracking: mention Azure Boards and Jira alongside Linear
- Fix limitation: Linear is built-in, others work via MCP
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Major restructure based on user feedback:
- Lead with onboarding as the key differentiator
- Add "Bring What You Have" section with two real examples:
tildelingsbrev parsing and existing OKR quality review
- Show iterative development process, not one-shot usage
- Stronger value proposition: OKR expert that learns your context
- Remove simplistic Q&A example that made plugin look like a form-filler
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace dry documentation-style README with problem-first structure:
lead with public sector pain points, show realistic interaction example,
add "when not to use" section, move badges to bottom.
132 lines (down from 280). Hook within 10 seconds.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
No plugins should promise future features. ROADMAP.md and BACKLOG.md
are internal planning documents, not public-facing.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
All 6 plugin READMEs now use identical installation section:
marketplace-first approach with /plugin browsing, then direct
settings.json as alternative. Replaces inconsistent mix of
git clone, plugin add, and JSON-only instructions.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
