← all publishers

navikt

@navikt source repo

Report this profile Claim this profile

• 135 skills
• 0 followers
• last month last updated

1. ▌
   Security Review 5 · navikt bundle

   Assess a design or change for security and privacy risks. Use for sensitive data, identity, authorization, trust boundaries, privileged operations or a requested security review; use the full-context identity implementation workflow to implement an authentication mechanism and the full-context architecture assessment workflow for broader design trade-offs.
   5 installs
2. ▌
   Klarsprak 3 · navikt bundle

   Write or edit clear Norwegian prose while preserving technical meaning and established domain terms. Use for unclear user-facing copy, documentation or PR text; use `dulting` when the task is to influence behavior through an intervention.
   5 installs
3. ▌
   API Design 3 · navikt

   Design or change a published API or event contract using consumer and compatibility evidence. Use for new endpoints, versioning, breaking changes or deprecation; use `kotlin-ktor` for framework implementation and `architecture-review` for wider system boundaries.
   5 installs
4. ▌
   Security Review 3 · navikt bundle

   Assess a design or change for security and privacy risks. Use for sensitive data, identity, authorization, trust boundaries, privileged operations or a requested security review; use `auth-overview` to implement an authentication mechanism and `architecture-review` for broader design trade-offs.
   5 installs
5. ▌
   Nav Troubleshoot 3 · navikt bundle

   Diagnose deployed Nais workload failures using deployment, pod, log, metric and trace evidence. Use for production-only errors, failed deploys, restarts or connectivity problems; use `diagnosing-bugs` once a code defect needs reproduction and a fix.
   1 install
6. ▌
   Postgresql Review 3 · navikt bundle

   Design or review PostgreSQL schemas, queries, transactions, migrations and connection capacity. Use for slow queries, pool sizing, data integrity or database changes; use `nav-troubleshoot` for deployed incident evidence and `architecture-review` for broader storage decisions.
   5 installs
7. ▌
   Observability Setup 3 · navikt bundle

   Add or improve service metrics, structured logs, traces, health signals, dashboards and alerts. Use when instrumentation or operational visibility is missing or misleading; use `nav-troubleshoot` to investigate an active incident with existing telemetry.
   5 installs
8. ▌
   Security Review 4 · navikt bundle

   Assess a design or change for security and privacy risks. Use for sensitive data, identity, authorization, trust boundaries, privileged operations or a requested security review; use the full-context identity implementation workflow to implement an authentication mechanism and the full-context architecture assessment workflow for broader design trade-offs.
   5 installs
9. ▌
   Pull Request 3 · navikt

   Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
   5 installs
10. ▌
    Pull Request 4 · navikt

    Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
    6 installs
11. ▌
    Doctor 2 · navikt

    Audit whether the current repository and session are ready for effective Grillmester use in OpenCode v1. Use only when the user explicitly asks to check, diagnose, or understand the OpenCode setup; the audit is read-only.
    5 installs
12. ▌
    Review 2 · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    4 installs
13. ▌
    Triage 2 · navikt bundle

    Assess incoming issues or pull requests, verify claims and prepare work-ready briefs. Use for inbox review, bug-report assessment or readiness decisions; use `issue-management` for tracker mutations and `review` for a completed implementation diff.
    6 installs
14. ▌
    Dulting 2 · navikt bundle

    Design and evaluate responsible behavioral interventions in public services. Use for reminders, defaults, friction or experiments intended to change a specific user behavior; use `klarsprak` when the task is only to clarify wording.
    5 installs
15. ▌
    Handoff 2 · navikt

    Prepare a portable handoff when the user requests transferring work to another session, client, or colleague. Ordinary context compression and same-session delegation belong to the client.
    6 installs
16. ▌
    To Spec 2 · navikt

    Document resolved requirements and design choices as a concise implementation plan or specification, including a requested local document. Use `grill-with-docs` for unresolved design choices and `to-issues` for several independently deliverable slices.
    8 installs
17. ▌
    Grill Me 2 · navikt

    Run an explicitly requested standalone stress-test of a plan, proposal, or idea. Use when the user asks to be grilled; expose weak assumptions and resolve choices in conversation without automatically creating documentation or a decision map.
    6 installs
18. ▌
    Grilling 2 · navikt

    Clarify a request and challenge a plan's assumptions, requirements, and trade-offs through one question at a time. Use for unresolved intent or design choices, and as Grillmester's opening method; grill-with-docs adds durable domain documentation and Wayfinder organizes dependent decisions.
    6 installs
19. ▌
    E2e Tests 2 · navikt

    Create full-system tests that boot the application and prove an observable user or system flow. Use when the assembled app, its entry point and final outcome must work together; use `integration-tests` for a narrow real adapter without full application boot.
    5 installs
20. ▌
    Klarsprak 2 · navikt bundle

    Write or edit clear Norwegian prose while preserving technical meaning and established domain terms. Use for unclear user-facing copy, documentation or PR text; use `dulting` when the task is to influence behavior through an intervention.
    3 installs
21. ▌
    Prototype 2 · navikt

    Build a bounded, runnable throwaway experiment to resolve uncertain behavior or an interface contract. Use for data models, state machines, event flows, retries or failure semantics; use `design-prototype` for visual layouts and user-flow sketches.
    8 installs
22. ▌
    To Issues 2 · navikt

    Turn a resolved plan or specification into independently useful implementation issues with native dependencies. Use when the user asks to break work into tickets; use `wayfinder` for unresolved decisions and `issue-management` for tracker mechanics.
    8 installs
23. ▌
    Wayfinder 2 · navikt bundle

    Organize several unresolved, dependent decisions as a persistent shared issue map when a conversation checkpoint cannot keep the route navigable across sessions. Select automatically from that need or continue an existing map; use grill-with-docs for each design decision, and ordinary planning when the direction is already settled.
    4 installs
24. ▌
    API Design 2 · navikt

    Design or change a published API or event contract using consumer and compatibility evidence. Use for new endpoints, versioning, breaking changes or deprecation; use `kotlin-ktor` for framework implementation and `architecture-review` for wider system boundaries.
    5 installs
25. ▌
    Tdd 3 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or the repository's full-system test workflow to choose the test boundary.
    3 installs
26. ▌
    Kafka Topic 2 · navikt bundle

    Design, implement or review Kafka topics and event flows from producer to consumer. Use for event contracts, keys, consumer groups, delivery guarantees or failure handling; use `nav-troubleshoot` for runtime incident evidence and `api-design` for wider contract compatibility.
    6 installs
27. ▌
    Kotlin Ktor 2 · navikt bundle

    Implement or review Kotlin and Ktor application behavior, configuration, clients and lifecycle. Use when changing a Ktor backend; use `api-design` for public contract choices and `auth-overview` for identity and authorization mechanisms.
    3 installs
28. ▌
    Lumi Survey 2 · navikt bundle

    Integrate or review @navikt/lumi-survey from frontend configuration through verified feedback submission. Use for Lumi widgets, survey choices, transport or privacy-safe context; use `auth-overview` for shared authentication design beyond the Lumi integration.
    3 installs
29. ▌
    Team Status 2 · navikt bundle

    Summarize team status, goal progress and priorities from confirmed work and outcome evidence. Use for weekly updates, period reviews or cross-repository overviews; use `okr` to formulate goals and `triage` to assess individual incoming issues.
    5 installs
30. ▌
    Aksel Design 2 · navikt bundle

    Choose Aksel components, semantic tokens and responsive patterns for Nav interfaces. Use when designing or changing layout, forms or styling with @navikt/ds-react; use `accessibility-review` to verify the resulting user flow.
    4 installs
31. ▌
    Pull Request 2 · navikt

    Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
    7 installs
32. ▌
    Auth Overview 2 · navikt bundle

    Design, implement or diagnose authentication and authorization in a Nav backend. Use for token validation, token exchange, protected endpoints or issuer, audience and 401/403 problems; use `security-review` for a broader security assessment.
    6 installs
33. ▌
    Guided Review 2 · navikt

    Guide a human through a pull request or resolved diff one reading step at a time, then prepare review findings. Manually invoke this workflow for an interactive assessment; use `review` for the normal self-review pass.
    5 installs
34. ▌
    Nais Manifest 2 · navikt bundle

    Create, change or review Nais Application and Naisjob deployment resources. Use for ingress, probes, resource limits, access policies, scaling or scheduled jobs; use `nav-troubleshoot` to diagnose a live workload and specialist skills for application code.
    7 installs
35. ▌
    Readme Update 2 · navikt

    Create or update a README from verified implementation and operational evidence. Use when repository purpose, setup, usage or ownership documentation is missing or stale; use `klarsprak` for a wording-only edit and `to-spec` for intended future behavior.
    5 installs
36. ▌
    Doctor 3 · navikt

    Audit whether the current repository and session are ready for effective Grillmester use in OpenCode v1. Use only when the user explicitly asks to check, diagnose, or understand the OpenCode setup; the audit is read-only.
    3 installs
37. ▌
    Tdd 4 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or the repository's full-system test workflow to choose the test boundary.
    5 installs
38. ▌
    Review 3 · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    8 installs
39. ▌
    Create A Skill 2 · navikt bundle

    Create, revise, review, or diagnose a portable Agent Skill for OpenCode v1, including native discovery, permissions, and an optional slash-command adapter. Use when a user asks to create or improve a skill, investigate why one does not load, or validate skill behavior.
    5 installs
40. ▌
    Figma Workflow 2 · navikt

    Translate a chosen Figma design into Aksel code or an implementation brief with component, token and responsive guidance. Use for design-to-code work; use `design-prototype` for visual exploration or changes to the Figma design itself. Design-only agents return a brief.
    3 installs
41. ▌
    Produktledelse 2 · navikt bundle

    Explore product opportunities, user needs, assumptions and initiative risks. Use for discovery planning, user interviews or product-lead reflection; use `okr` for measurable goals and `workshop-design` for a facilitated group session.
    5 installs
42. ▌
    Diagnosing Bugs 2 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and `nav-troubleshoot` when the missing evidence is in a deployed Nais environment.
    5 installs
43. ▌
    Domain Modeling 2 · navikt bundle

    Challenge and maintain canonical domain terminology and qualifying architectural decisions during authorized design work. Use when concepts, boundaries, or durable trade-offs change; reading existing vocabulary alone does not need this skill.
    5 installs
44. ▌
    Grill With Docs 2 · navikt

    Resolve open requirements, assumptions or design choices against the repository's domain model, recording agreed terms and qualifying decisions. Use for coherent design clarification; use `to-spec` to capture a settled plan and `wayfinder` for dependent decisions needing a persistent map.
    9 installs
45. ▌
    Security Review 2 · navikt bundle

    Assess a design or change for security and privacy risks. Use for sensitive data, identity, authorization, trust boundaries, privileged operations or a requested security review; use `auth-overview` to implement an authentication mechanism and `architecture-review` for broader design trade-offs.
    6 installs
46. ▌
    Workshop Design 2 · navikt bundle

    Design a facilitated workshop with an outcome, agenda, participation structure and follow-up. Use for group exploration, alignment, decisions, retrospectives or team health; use `produktledelse` for individual discovery guidance and `okr` for goal formulation.
    6 installs
47. ▌
    Design Prototype 2 · navikt bundle

    Explore or refine visual concepts, user flows and existing Figma designs through Aksel browser sketches or editable Figma components. Use for layout, hierarchy and visual alternatives; use `prototype` for executable behavior and `figma-workflow` to translate a chosen design into code or an implementation brief.
    6 installs
48. ▌
    Issue Management 2 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use `triage` to assess readiness and `to-issues` to decompose a resolved plan.
    4 installs
49. ▌
    Nav Troubleshoot 2 · navikt bundle

    Diagnose deployed Nais workload failures using deployment, pod, log, metric and trace evidence. Use for production-only errors, failed deploys, restarts or connectivity problems; use `diagnosing-bugs` once a code defect needs reproduction and a fix.
    8 installs
50. ▌
    Review 4 · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    6 installs
51. ▌
    Integration Tests 2 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use `e2e-tests` when proving the flow requires booting the assembled application.
    7 installs
52. ▌
    Postgresql Review 2 · navikt bundle

    Design or review PostgreSQL schemas, queries, transactions, migrations and connection capacity. Use for slow queries, pool sizing, data integrity or database changes; use `nav-troubleshoot` for deployed incident evidence and `architecture-review` for broader storage decisions.
    5 installs
53. ▌
    Architecture Review 2 · navikt bundle

    Evaluate a consequential architecture proposal, its alternatives, migration and reversibility. Use for new services, cross-team boundaries, platform choices or costly migrations; use `improve-codebase-architecture` to discover refactoring candidates in existing code and `security-review` for security analysis.
    5 installs
54. ▌
    Observability Setup 2 · navikt bundle

    Add or improve service metrics, structured logs, traces, health signals, dashboards and alerts. Use when instrumentation or operational visibility is missing or misleading; use `nav-troubleshoot` to investigate an active incident with existing telemetry.
    5 installs
55. ▌
    Accessibility Review 2 · navikt

    Review a Nav frontend flow for accessibility using keyboard, screen-reader, contrast, focus, form and axe evidence. Use when checking an interface before delivery or investigating an accessibility defect; use `aksel-design` for component selection and layout.
    3 installs
56. ▌
    Create A Skill 3 · navikt bundle

    Create, revise, review, or diagnose a portable Agent Skill for OpenCode v1, including native discovery, permissions, and an optional slash-command adapter. Use when a user asks to create or improve a skill, investigate why one does not load, or validate skill behavior.
    5 installs
57. ▌
    Diagnosing Bugs 3 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and the repository's platform diagnostic workflow when the missing evidence is in a deployed Nais environment.
    8 installs
58. ▌
    Issue Management 3 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use the full-context issue assessment workflow to assess readiness and the full-context plan decomposition workflow to decompose a resolved plan.
    4 installs
59. ▌
    Integration Tests 3 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use the repository's full-system test workflow when proving the flow requires booting the assembled application.
    6 installs
60. ▌
    Diagnosing Bugs 4 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and the repository's platform diagnostic workflow when the missing evidence is in a deployed Nais environment.
    5 installs
61. ▌
    Issue Management 4 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use the full-context issue assessment workflow to assess readiness and the full-context plan decomposition workflow to decompose a resolved plan.
    4 installs
62. ▌
    Integration Tests 4 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use the repository's full-system test workflow when proving the flow requires booting the assembled application.
    7 installs
63. ▌
    Improve Codebase Architecture 2 · navikt bundle

    Find refactoring opportunities that simplify module boundaries and improve testability and navigation. Use when existing code is tightly coupled, shallow or hard to change; use `architecture-review` to evaluate a concrete architecture proposal.
    5 installs
64. ▌
    Okr 2 · navikt bundle

    Formulate and review measurable product outcomes with objectives, key results, baselines and evidence. Use for goal setting or turning delivery lists into outcome measures; use `team-status` to report progress against existing goals.
    4 installs
65. ▌
    Tdd 2 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or `e2e-tests` to choose the test boundary.
    5 installs
66. ▌
    Okr · navikt bundle

    Formulate and review measurable product outcomes with objectives, key results, baselines and evidence. Use for goal setting or turning delivery lists into outcome measures; use `team-status` to report progress against existing goals.
    4 installs
67. ▌
    Tdd · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or `e2e-tests` to choose the test boundary.
    5 installs
68. ▌
    Doctor · navikt

    Audits whether the current repository is ready for effective Grillmester use across Copilot CLI, the Copilot app, cloud agent, and Copilot code review. Use only when the user explicitly asks to check, diagnose, or understand the repository's Grillmester setup; the audit is read-only.
    7 installs
69. ▌
    Review · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    3 installs
70. ▌
    Triage · navikt bundle

    Assess incoming issues or pull requests, verify claims and prepare work-ready briefs. Use for inbox review, bug-report assessment or readiness decisions; use `issue-management` for tracker mutations and `review` for a completed implementation diff.
    4 installs
71. ▌
    Dulting · navikt bundle

    Design and evaluate responsible behavioral interventions in public services. Use for reminders, defaults, friction or experiments intended to change a specific user behavior; use `klarsprak` when the task is only to clarify wording.
    3 installs
72. ▌
    Handoff · navikt

    Prepare a portable handoff when the user requests transferring work to another session, client, or colleague. Ordinary context compression and same-session delegation belong to the client.
    6 installs
73. ▌
    To Spec · navikt

    Document resolved requirements and design choices as a concise implementation plan or specification, including a requested local document. Use `grill-with-docs` for unresolved design choices and `to-issues` for several independently deliverable slices.
    9 installs
74. ▌
    Grill Me · navikt

    Run an explicitly requested standalone stress-test of a plan, proposal, or idea. Use when the user asks to be grilled; expose weak assumptions and resolve choices in conversation without automatically creating documentation or a decision map.
    7 installs
75. ▌
    Grilling · navikt

    Clarify a request and challenge a plan's assumptions, requirements, and trade-offs through one question at a time. Use for unresolved intent or design choices, and as Grillmester's opening method; grill-with-docs adds durable domain documentation and Wayfinder organizes dependent decisions.
    5 installs
76. ▌
    E2e Tests · navikt

    Create full-system tests that boot the application and prove an observable user or system flow. Use when the assembled app, its entry point and final outcome must work together; use `integration-tests` for a narrow real adapter without full application boot.
    4 installs
77. ▌
    Prototype · navikt

    Build a bounded, runnable throwaway experiment to resolve uncertain behavior or an interface contract. Use for data models, state machines, event flows, retries or failure semantics; use `design-prototype` for visual layouts and user-flow sketches.
    4 installs
78. ▌
    To Issues · navikt

    Turn a resolved plan or specification into independently useful implementation issues with native dependencies. Use when the user asks to break work into tickets; use `wayfinder` for unresolved decisions and `issue-management` for tracker mechanics.
    10 installs
79. ▌
    Wayfinder · navikt bundle

    Organize several unresolved, dependent decisions as a persistent shared issue map when a conversation checkpoint cannot keep the route navigable across sessions. Select automatically from that need or continue an existing map; use grill-with-docs for each design decision, and ordinary planning when the direction is already settled.
    3 installs
80. ▌
    Kafka Topic · navikt bundle

    Design, implement or review Kafka topics and event flows from producer to consumer. Use for event contracts, keys, consumer groups, delivery guarantees or failure handling; use `nav-troubleshoot` for runtime incident evidence and `api-design` for wider contract compatibility.
    6 installs
81. ▌
    Kotlin Ktor · navikt bundle

    Implement or review Kotlin and Ktor application behavior, configuration, clients and lifecycle. Use when changing a Ktor backend; use `api-design` for public contract choices and `auth-overview` for identity and authorization mechanisms.
    4 installs
82. ▌
    Lumi Survey · navikt bundle

    Integrate or review @navikt/lumi-survey from frontend configuration through verified feedback submission. Use for Lumi widgets, survey choices, transport or privacy-safe context; use `auth-overview` for shared authentication design beyond the Lumi integration.
    5 installs
83. ▌
    Team Status · navikt bundle

    Summarize team status, goal progress and priorities from confirmed work and outcome evidence. Use for weekly updates, period reviews or cross-repository overviews; use `okr` to formulate goals and `triage` to assess individual incoming issues.
    5 installs
84. ▌
    Aksel Design · navikt bundle

    Choose Aksel components, semantic tokens and responsive patterns for Nav interfaces. Use when designing or changing layout, forms or styling with @navikt/ds-react; use `accessibility-review` to verify the resulting user flow.
    3 installs
85. ▌
    Pull Request · navikt

    Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
    9 installs
86. ▌
    Auth Overview · navikt bundle

    Design, implement or diagnose authentication and authorization in a Nav backend. Use for token validation, token exchange, protected endpoints or issuer, audience and 401/403 problems; use `security-review` for a broader security assessment.
    2 installs
87. ▌
    Guided Review · navikt

    Guide a human through a pull request or resolved diff one reading step at a time, then prepare review findings. Manually invoke this workflow for an interactive assessment; use `review` for the normal self-review pass.
    6 installs
88. ▌
    Nais Manifest · navikt bundle

    Create, change or review Nais Application and Naisjob deployment resources. Use for ingress, probes, resource limits, access policies, scaling or scheduled jobs; use `nav-troubleshoot` to diagnose a live workload and specialist skills for application code.
    4 installs
89. ▌
    Readme Update · navikt

    Create or update a README from verified implementation and operational evidence. Use when repository purpose, setup, usage or ownership documentation is missing or stale; use `klarsprak` for a wording-only edit and `to-spec` for intended future behavior.
    7 installs
90. ▌
    Create A Skill · navikt bundle

    Create, improve or diagnose a GitHub Copilot CLI skill and validate its discovery and behavior. Use when authoring instructions, correcting triggers or testing skill selection; explicit repository setup audits belong to `doctor`.
    5 installs
91. ▌
    Figma Workflow · navikt

    Translate a chosen Figma design into Aksel code or an implementation brief with component, token and responsive guidance. Use for design-to-code work; use `design-prototype` for visual exploration or changes to the Figma design itself. Design-only agents return a brief.
    5 installs
92. ▌
    Produktledelse · navikt bundle

    Explore product opportunities, user needs, assumptions and initiative risks. Use for discovery planning, user interviews or product-lead reflection; use `okr` for measurable goals and `workshop-design` for a facilitated group session.
    5 installs
93. ▌
    Diagnosing Bugs · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and `nav-troubleshoot` when the missing evidence is in a deployed Nais environment.
    3 installs
94. ▌
    Domain Modeling · navikt bundle

    Challenge and maintain canonical domain terminology and qualifying architectural decisions during authorized design work. Use when concepts, boundaries, or durable trade-offs change; reading existing vocabulary alone does not need this skill.
    5 installs
95. ▌
    Grill With Docs · navikt

    Resolve open requirements, assumptions or design choices against the repository's domain model, recording agreed terms and qualifying decisions. Use for coherent design clarification; use `to-spec` to capture a settled plan and `wayfinder` for dependent decisions needing a persistent map.
    7 installs
96. ▌
    Workshop Design · navikt bundle

    Design a facilitated workshop with an outcome, agenda, participation structure and follow-up. Use for group exploration, alignment, decisions, retrospectives or team health; use `produktledelse` for individual discovery guidance and `okr` for goal formulation.
    6 installs
97. ▌
    Design Prototype · navikt bundle

    Explore or refine visual concepts, user flows and existing Figma designs through Aksel browser sketches or editable Figma components. Use for layout, hierarchy and visual alternatives; use `prototype` for executable behavior and `figma-workflow` to translate a chosen design into code or an implementation brief.
    6 installs
98. ▌
    Issue Management · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use `triage` to assess readiness and `to-issues` to decompose a resolved plan.
    6 installs
99. ▌
    Integration Tests · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use `e2e-tests` when proving the flow requires booting the assembled application.
    10 installs
100. ▌
     Architecture Review · navikt bundle

     Evaluate a consequential architecture proposal, its alternatives, migration and reversibility. Use for new services, cross-team boundaries, platform choices or costly migrations; use `improve-codebase-architecture` to discover refactoring candidates in existing code and `security-review` for security analysis.
     6 installs