@monoes/monomindcli 2.15.3 → 2.15.4

package/org-skills/change-management/references/change-playbook.md

@@ -0,0 +1,308 @@
+# Change Management Playbook
+
+Deep reference for rolling out organizational changes effectively.
+
+---
+
+## 1. ADKAR Deep Dive with Startup Examples
+
+### Awareness: The "Why" that actually lands
+
+Most change communications fail at awareness because they confuse informing with explaining.
+
+**Informing:** "We're moving from Jira to Linear next month."
+**Explaining:** "Our engineering team loses ~4 hours per week to Jira configuration, search latency, and reporting setup. At our current team size, that's 60+ hours per month. Linear's benchmarks from teams our size show a 40% reduction in that overhead. That's why we're switching — and here's the timeline."
+
+The explanation activates desire. The announcement just creates work.
+
+**Real example: Tool migration**
+> "We tried Asana, we tried Notion tasks, we tried spreadsheets. None of them stuck. After talking to 8 engineering leads at similar companies, the pattern was clear: teams that use Linear stick with it. We're going all-in. Here's why it will be different this time: [specific reasons]."
+
+**Real example: Reorg**
+> "The current structure has our customer success team reporting to Sales, which creates a conflict: Sales is measured on new logo count, CS is measured on retention. We've seen this play out in three recent customer losses where CS needed to raise concerns but felt the pressure to stay quiet. We're changing the reporting structure so CS reports directly to me. This is about removing a structural conflict, not about performance."
+
+---
+
+### Desire: Addressing the "What's in it for me?"
+
+Every stakeholder group needs a different answer.
+
+**Individual contributor:**
+- "Will my job change significantly?"
+- "Will this make my day easier or harder?"
+- "Is my role at risk?"
+
+**Manager:**
+- "What new responsibilities do I take on?"
+- "How do I explain this to my team?"
+- "What happens if someone on my team doesn't adapt?"
+
+**Senior leader:**
+- "What does this change our strategic posture?"
+- "What resources are reallocated and to what?"
+- "How does this affect my relationships with other senior leaders?"
+
+**Resistance scenario: Senior leader whose team is most affected**
+> They're supportive in the room, silent or undermining outside it.
+> Fix: Give them a role in the change. Make them a named co-leader of the implementation. Invested people don't undermine.
+
+---
+
+### Knowledge: The documentation that actually gets used
+
+The reason most change documentation fails: it's written for the decision-maker, not the user.
+
+**Documentation that gets used:**
+- Short (< 2 pages for most changes)
+- Organized by role: "If you're in Sales, here's what changes for you"
+- Answers "what do I do when X happens?" with specific answers
+- Has a clear owner: "Questions? Ask [person] in #channel"
+
+**Documentation that doesn't get used:**
+- Long rationale sections the user doesn't need
+- "See the full policy document for details"
+- No named point of contact
+- Buried in email threads
+
+---
+
+### Ability: The gap between knowing and doing
+
+Signs of a knowledge gap vs. an ability gap:
+
+| Symptom | Knowledge gap | Ability gap |
+|---------|-------------|------------|
+| People don't know what to do | ✅ | |
+| People know what to do but don't do it | | ✅ |
+| People do it wrong consistently | Could be either | |
+| People revert under pressure | | ✅ |
+| Training scores high, behavior unchanged | | ✅ |
+
+**Ability gaps are fixed by:**
+1. Practice time (before being measured)
+2. Reduced cognitive load during transition
+3. Peer support (not just manager support)
+4. Feedback loops that are fast and low-stakes
+
+**What kills ability development:**
+- Measuring performance on the new way in week 1
+- Adding new work simultaneously with the change
+- Making it embarrassing to ask for help
+
+---
+
+### Reinforcement: The phase everyone skips
+
+Go-live is not success. Go-live is the beginning of adoption.
+
+**Reinforcement calendar (template):**
+
+| Week | Action |
+|------|--------|
+| Week 1 (go-live) | High-visibility support. Leadership visible. Point person responsive. |
+| Week 2 | First adoption check: who's using it? Who isn't? Targeted help to laggards. |
+| Week 4 | Celebrate early adopters publicly. Share a win story. |
+| Week 6 | Adoption metric reported to leadership. Decommission old way (if applicable). |
+| Week 8 | Full adoption expected. Non-adoption now a performance conversation. |
+| Month 3 | Retrospective: What's working? What needs adjustment? |
+
+---
+
+## 2. Resistance Patterns and Counter-Strategies
+
+### The Vocal Skeptic
+
+**Who they are:** Asks hard questions in all-hands. Other people follow their lead.
+**What they need:** To feel heard and to understand the logic.
+**Strategy:** Talk to them before the all-hands. Not to persuade them — to hear their concerns and address what's valid. When they feel respected, they often become your best change advocates.
+
+**Script:** "I know you have concerns about this change. I want to understand them before we go broader with the announcement. What's your biggest worry?"
+
+---
+
+### The Silent Non-Complier
+
+**Who they are:** Agrees in meetings, continues the old behavior outside.
+**What they need:** To understand that non-compliance is visible and has consequences.
+**Strategy:** Direct 1:1 conversation. Name the behavior. Ask what's in the way. Give them a clear path.
+
+**Script:** "I've noticed you're still using [old way] two weeks after we launched [new way]. I want to understand what's in the way for you — is it a knowledge issue, a time issue, or something else?"
+
+---
+
+### The Grieving Top Performer
+
+**Who they are:** Was excellent under the old system. The change makes their skills less relevant.
+**What they need:** Recognition of their past contribution and a clear path forward.
+**Strategy:** Name the loss explicitly. "I know you built your expertise on [old approach] and this change asks you to develop a new one. That's a real transition." Then create a specific development plan.
+
+**What not to do:** Pretend the change doesn't affect them disproportionately.
+
+---
+
+### The Fearful Middle Manager
+
+**Who they are:** Middle managers whose authority or role scope is reduced by the change.
+**What they need:** A clear picture of their new role and why it's still valuable.
+**Strategy:** Individual conversation before the announcement. Walk them through what changes, what stays the same, and what their contribution looks like in the new world.
+
+---
+
+### The "We've Been Here Before" Cynics
+
+**Who they are:** Long-tenured employees who've seen multiple failed change initiatives.
+**What they need:** Evidence that this time is different.
+**Strategy:** Acknowledge the history. "I know we've announced changes that didn't stick. Here's specifically what's different this time: [specific differences]." Then prove it fast — show momentum in the first 30 days.
+
+---
+
+## 3. Communication Plan Template per Change Type
+
+### Template: Tool Migration
+
+```
+COMMUNICATION PLAN — [Tool Name] Migration
+
+AUDIENCE: All-hands / [specific team]
+DECISION OWNER: [Name]
+GO-LIVE DATE: [Date]
+POINT OF CONTACT: [Name] in [channel]
+
+COMMUNICATION TIMELINE:
+Week -4: Decision finalized (internal only)
+Week -3: Training materials ready
+Week -2: All-hands announcement (why + timeline + support plan)
+Week -1: Training sessions (2 sessions, different times)
+Week 0: Go-live. Point person in Slack. Old system still accessible.
+Week 2: First adoption check. Targeted help to non-adopters.
+Week 4: Old system access restricted.
+Week 8: Old system fully decommissioned.
+
+KEY MESSAGES:
+- Why we're switching: [honest 2-sentence reason]
+- What changes for you: [role-specific, max 3 bullets]
+- What doesn't change: [this matters for change fatigue]
+- How to get help: [channel, person, office hours]
+- Timeline: [specific dates]
+
+FAQ:
+Q: Is the old system going away completely?
+A: [Honest answer with date]
+Q: What if I have data in the old system?
+A: [Migration plan or acknowledgment]
+Q: What if I'm not proficient by go-live?
+A: [Realistic expectation-setting]
+```
+
+### Template: Reorg Announcement
+
+```
+REORG COMMUNICATION PLAN
+
+ANNOUNCEMENT DATE: [Date]
+EFFECTIVE DATE: [Date]
+FORMAT: Live (synchronous), all affected employees
+
+PRE-ANNOUNCEMENT (1 week before):
+- 1:1 with every affected leader
+- HR briefed and ready for questions
+- FAQ prepared
+
+ANNOUNCEMENT FORMAT:
+1. Context: Why this change? (2-3 minutes)
+2. What's changing: New structure, new reporting lines (3-4 minutes)
+3. What's NOT changing: Roles, comp, team members (2 minutes)
+4. Timeline: When does the new structure take effect? (1 minute)
+5. Q&A: Open, no time limit (at least 15 minutes)
+
+POST-ANNOUNCEMENT (week 1):
+- Each manager runs team meeting to answer team-specific questions
+- HR available for private conversations
+- FAQ published to all
+
+POST-ANNOUNCEMENT (week 2-4):
+- New structure is operational
+- Transition check-in: what questions emerged that weren't anticipated?
+
+THINGS NOT TO SAY:
+- "We can't share why [person] is leaving" (if they are)
+- "This affects everyone equally" (it doesn't)
+- "No one's job is at risk" (unless this is 100% certain)
+```
+
+---
+
+## 4. The Change Fatigue Problem
+
+### How organizations develop change fatigue
+
+**Phase 1 — Excitement (first 1-2 changes):** People engage, try the new way, hope it sticks.
+
+**Phase 2 — Skepticism (3-5 changes):** People comply but hedge. "Let's see if this one lasts."
+
+**Phase 3 — Detachment (6+ changes without completion):** People stop investing in changes. Compliance is surface-level. New announcements get eye-rolls.
+
+**Phase 4 — Cynicism (entrenched fatigue):** People actively resist changes. "We've been here before." High performers leave because they don't want to work in a chaotic environment.
+
+### The change inventory audit
+
+**Run this before announcing any new change:**
+
+| Change | Status | Started | Expected complete |
+|--------|--------|---------|-----------------|
+| [Change 1] | In progress / Complete / Stalled | | |
+| [Change 2] | | | |
+| [Change 3] | | | |
+
+**Rules:**
+- If > 2 significant changes are in progress, don't start a third
+- If any change is stalled, diagnose it before starting something new
+- Define "complete" for every change in progress
+
+### Recovery from change fatigue
+
+1. **Declare a change moratorium.** "We're not starting anything new for 60 days. We're finishing what we started."
+2. **Complete visible wins.** Ship the changes that are 80% done. Demonstrate follow-through.
+3. **Communicate stability.** "Here's what is NOT changing this year."
+4. **Slow down the next announcement.** More preparation, more consultation, clearer "this time is different" evidence.
+
+---
+
+## 5. Measuring Adoption vs. Compliance
+
+Most change leaders measure go-live, not adoption. These are different things.
+
+### Adoption metrics by change type
+
+**Tool migration:**
+- % of team actively using the new tool (not just logged in)
+- % of relevant workflows completed in new tool vs. old tool
+- Support ticket volume in weeks 1-4 (high = knowledge gap; dropping = adoption)
+
+**Process change:**
+- % of relevant transactions following new process
+- Error rates in new process vs. old process (should converge over time)
+- Time-to-complete for new process (should improve by week 4)
+
+**Org change:**
+- Decision cycle time in new structure (should improve by month 2)
+- Escalation patterns (fewer cross-boundary escalations = alignment improving)
+- Employee sentiment (survey at months 1, 3, 6)
+
+**Culture change:**
+- Values referenced in 1:1 conversations (manager self-report)
+- Values-linked recognition events per month
+- Culture survey scores in relevant dimensions (quarterly)
+
+### The compliance trap
+
+Measuring compliance: "Did they use the new system? Yes/No."
+Measuring adoption: "Did they use the new system because it's better, or because they had to?"
+
+Compliance is unstable. It reverts when enforcement loosens. Adoption is self-sustaining.
+
+**Adoption diagnostic:** Ask a random sample: "Why do you use [new way] instead of [old way]?"
+- "Because I have to" = compliance
+- "Because it's faster/easier/better" = adoption
+
+Only adoption makes the change permanent.

package/org-skills/changelog-automation/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Seth Hobson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE. 

package/org-skills/changelog-automation/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: changelog-automation
+description: "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions."
+tags: ["engineering","devops","writing"]
+tools: []
+license: MIT
+source: https://github.com/wshobson/agents
+source_path: "plugins/documentation-generation/skills/changelog-automation"
+source_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620
+---
+# Changelog Automation
+
+Patterns and tools for automating changelog generation, release notes, and version management following industry standards.
+
+## When to Use This Skill
+
+- Setting up automated changelog generation
+- Implementing Conventional Commits
+- Creating release note workflows
+- Standardizing commit message formats
+- Generating GitHub/GitLab release notes
+- Managing semantic versioning
+
+## Core Concepts
+
+### 1. Keep a Changelog Format
+
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## Detailed patterns and worked examples
+
+Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
+
+## Summary
+
+This release introduces dark mode support and improves checkout performance
+by 40%. It also includes important security updates.
+
+## Highlights
+
+### 🌙 Dark Mode
+
+Users can now switch to dark mode from settings. The preference is
+automatically saved and synced across devices.
+
+### ⚡ Performance
+
+- Checkout flow is 40% faster
+- Reduced bundle size by 15%
+
+## Breaking Changes
+
+None in this release.
+
+## Upgrade Guide
+
+No special steps required. Standard deployment process applies.
+
+## Known Issues
+
+- Dark mode may flicker on initial load (fix scheduled for v2.1.1)
+
+## Dependencies Updated
+
+| Package | From    | To      | Reason                   |
+| ------- | ------- | ------- | ------------------------ |
+| react   | 18.2.0  | 18.3.0  | Performance improvements |
+| lodash  | 4.17.20 | 4.17.21 | Security patch           |
+```
+
+## Commit Message Examples
+
+```bash
+# Feature with scope
+feat(auth): add OAuth2 support for Google login
+
+# Bug fix with issue reference
+fix(checkout): resolve race condition in payment processing
+
+Closes #123
+
+# Breaking change
+feat(api)!: change user endpoint response format
+
+BREAKING CHANGE: The user endpoint now returns `userId` instead of `id`.
+Migration guide: Update all API consumers to use the new field name.
+
+# Multiple paragraphs
+fix(database): handle connection timeouts gracefully
+
+Previously, connection timeouts would cause the entire request to fail
+without retry. This change implements exponential backoff with up to
+3 retries before failing.
+
+The timeout threshold has been increased from 5s to 10s based on p99
+latency analysis.
+
+Fixes #456
+Reviewed-by: @alice
+```
+
+## Best Practices
+
+### Do's
+
+- **Follow Conventional Commits** - Enables automation
+- **Write clear messages** - Future you will thank you
+- **Reference issues** - Link commits to tickets
+- **Use scopes consistently** - Define team conventions
+- **Automate releases** - Reduce manual errors
+
+### Don'ts
+
+- **Don't mix changes** - One logical change per commit
+- **Don't skip validation** - Use commitlint
+- **Don't manual edit** - Generated changelogs only
+- **Don't forget breaking changes** - Mark with `!` or footer
+- **Don't ignore CI** - Validate commits in pipeline