feat: add okr plugin v1.0.0 — OKR guidance for Norwegian public sector

Expert OKR guidance based on Google/Doerr methodology, adapted for
4-month tertial cycles and Norwegian government accountability.

Components:
- 8 commands (skriv, kvalitet, kaskade, sporing, møter, innføring, governance, oppsett)
- 5 agents (kvalitetssjekker, kaskadebygger, fremdriftssporer, møtefasilitator, styringsrådgiver)
- 3 hooks (UserPromptSubmit context injection, PreCompact state preservation, Stop reminder)
- 15 reference files covering methodology, governance, meetings, antipatterns
- Linear MCP integration for OKR tracking

Previously in ktg-privat, now open-sourced.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

plugins/okr/CONTRIBUTING.md

@@ -0,0 +1,64 @@
+# Contributing to OKR Offentlig Sektor
+
+Takk for at du vil bidra til OKR-pluginen!
+
+## How to Contribute
+
+### Reporting Bugs
+
+1. Check existing issues to avoid duplicates
+2. Open a new issue with:
+   - Clear description of the problem
+   - Steps to reproduce
+   - Expected vs actual behavior
+   - Your environment (OS, Claude Code version)
+
+### Suggesting Features
+
+1. Open an issue with the "enhancement" label
+2. Describe the use case and expected behavior
+3. Explain why this would benefit other users
+4. Consider public sector context and constraints
+
+### Submitting Pull Requests
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/my-feature`)
+3. Make your changes
+4. Test thoroughly with `/okr` commands
+5. Commit with clear messages (`feat:`, `fix:`, `docs:`)
+6. Push and open a PR
+
+## Development Setup
+
+1. Clone the repo
+2. Add to your Claude Code plugins:
+   ```json
+   {
+     "plugins": ["path/to/okr"]
+   }
+   ```
+3. Restart Claude Code
+4. Run `/okr` to verify installation
+
+## Code Style
+
+- Follow existing patterns in the codebase
+- Use YAML frontmatter for all commands/agents
+- Keep commands focused and single-purpose
+- **Norwegian** for user-facing text (commands, descriptions)
+- **English** for code, config, and documentation structure
+- Document new features in README.md
+
+## OKR Domain Knowledge
+
+When contributing OKR-related content:
+
+- Follow Google/Doerr methodology
+- Consider 4-month cycle constraints (Norwegian public sector)
+- Include examples relevant to public sector
+- Reference Oboard tracking where applicable
+
+## Questions?
+
+Open an issue with the "question" label.