- [ ] **Define plugin policy tiers.**
→ *Create three lists in `/docs/ide_plugins.md`: **Mandatory**, **Recommended**, **Allowed/Optional** (and a short **Prohibited** section if needed, for example Copilot to force learning by doing on your own).*
- [ ] **Question:** Which plugins are **mandatory** for collaboration?
→ *Include tooling that enforces team standards (e.g. **Conventional Commits** helper, code formatter, linter integration, Git integration). List exact plugin names/IDs per IDE.*
- [ ] **Add a minimal “starter set” per IDE.**
→ *For VS Code, PyCharm/IntelliJ, Sublime: provide install steps/commands and versions. Store as `/config/ide/plugins_<ide>.txt`.*
- [ ] **Question:** How will you evaluate new plugins?
→ *Define acceptance criteria (compatibility, team value, performance, security, maintenance). Document a short checklist in `/docs/ide_plugins.md`.*
- [ ] **Version pinning & compatibility.**
→ *Record tested plugin versions and IDE versions; re-verify after IDE upgrades. Note any known conflicts and workarounds.*
- [ ] **Conventional Commits support (recommended/mandatory).**
→ *Select and list plugins or tools that assist commit message templates/validation within the IDE; cross-link to your “Commit Style” doc.*
- [ ] **Formatting & linting alignment.**
→ *Require formatter/linter plugins that read project config files (`.editorconfig`, `pyproject.toml`, `eslint.config.js`, etc.). Ensure “format on save” is consistent across IDEs.*
- [ ] **Question:** What is the approval and rollout process?
→ *Propose plugin changes via an issue labeled `ide-plugins`. One reviewer approves; then update `/docs/ide_plugins.md` and the per-IDE plugin lists.*
- [ ] **Export/import plugin sets.**
→ *Document how to export installed plugins (JetBrains “Export Settings”, VS Code `--list-extensions`) and how to import from the team lists. Verify on at least two OSes.*
- [ ] **Performance & troubleshooting.**
→ *Add a quick guide for diagnosing slowdowns (disable suspects, safe mode, index rebuild). Keep a “Known Issues” section with fixes.*
- [ ] **Security & privacy notes.**
→ *Prefer well-maintained, reputable plugins; avoid those requesting excessive permissions. Add a one-line rationale for any unusual plugin.*
- [ ] **Onboarding check.**
→ *Open an issue “IDE Plugins Verified” where each member posts their IDE, version, OS, and plugin tier status (✅/❌).*