@monoes/monomindcli 2.15.3 → 2.15.4

package/org-skills/general-counsel-advisor/references/term_sheet_decoder.md

@@ -0,0 +1,243 @@
+# Term Sheet Decoder
+
+Glossary + founder-friendly defaults + pushback strategies for every clause in a standard venture term sheet. **Not legal advice.** Always engage venture / securities counsel before responding.
+
+## The Three Clauses That Matter Most
+
+In any term sheet review, focus disproportionately on these three. They drive ~80% of the founder economics impact.
+
+### 1. Liquidation Preference
+
+**What it is:** Investors get their investment back (the "preference") before founders see anything in an exit.
+
+**The dimensions:**
+
+- **Multiple:** 1x (standard) means $1 back per $1 invested. 2x means $2 back. Higher = more hostile.
+- **Participating vs Non-participating:**
+  - **Non-participating (founder-friendly):** Investor chooses preference OR convert to common at exit. Most exits hit the conversion threshold, so preference is effectively just downside protection.
+  - **Participating ("double-dip"):** Investor gets preference back AND a pro-rata share of remaining proceeds as if converted. Significantly increases investor take in mid-range exits.
+- **Cap:** Caps the total return at, say, 2x or 3x of investment for participating preferences. Limits the double-dip.
+
+**Standard (Series A/B):** 1x non-participating.
+
+**Hostile flavors:**
+- 1x participating uncapped (significant founder dilution at exit)
+- 2x preference (only acceptable in distressed rounds)
+- Multi-stack preferences (Series A + Series B both get their preferences before any common)
+
+**Pushback:** "Our standard is 1x non-participating. Participating preferences create misalignment with management at exit."
+
+### 2. Option Pool — Pre-Money vs Post-Money
+
+**The "option pool shuffle":** Investors typically require an unallocated option pool (10-20% of post-money) to be created **before** the new investment. If this comes out of pre-money, founders are diluted; if post-money, all shareholders dilute proportionally.
+
+**Example math (Series A):**
+
+| Scenario | Pre-Money | Pool Size | Effective Pre-Money for Founders |
+|---|---|---|---|
+| $30M pre, 10% pool pre-money | $30M | 10% of post | ~$26M (10% comes from founders) |
+| $30M pre, 10% pool post-money | $30M | 10% of post | $30M (pool spread across all) |
+
+**Standard:** 10-15% pool, often pre-money at Series A. Founder-friendly: smaller pool or post-money.
+
+**Pushback:** "We've modeled our hiring plan and 8% supports the next 18 months. Let's right-size to actual need, not standard percentage." Or: "Pool top-up should come out of post-money so the new investor shares the dilution."
+
+### 3. Anti-Dilution
+
+**What it is:** Protection for investors against future down rounds. If a later round prices below the current, the current investor's price is adjusted retroactively.
+
+**Flavors (least to most hostile):**
+
+- **None:** Rare; only in seed SAFEs sometimes.
+- **Broad-based weighted average (standard):** Adjusts using all shares (common, options, warrants). Modest founder dilution in a down round.
+- **Narrow-based weighted average:** Uses only preferred. More dilutive than broad-based.
+- **Full ratchet (hostile):** Investor's price resets entirely to the new round's price. Massively dilutive to founders.
+
+**Standard:** Broad-based weighted average.
+
+**Pushback:** "Full ratchet is non-starter at this stage. Narrow-based is unusual. We need broad-based weighted average — this is the NVCA standard."
+
+---
+
+## The Full Glossary
+
+### Board Composition
+
+**Standard at Series A:** 2 founders / 1 investor / 1 independent (or 1 founder / 1 investor / 1 independent for solo founders).
+
+**At Series B:** Often 2 / 2 / 1 (balanced with independent tie-breaker).
+
+**At Series C+:** Often investors get majority (signals control transition).
+
+**Founder protection:** Always insist on the independent seat. Independent directors prevent deadlock and provide a neutral voice.
+
+**Pushback on investor-majority boards at A:** "Investor control of the board at Series A is premature. Let's keep founder control with an independent tie-breaker until Series B."
+
+### Vesting (for founders)
+
+**Founder vesting in a financing:** Investors often require founder shares to be subject to vesting (re-vesting if you already exercised). Standard: 4 years, 1-year cliff. Often the cliff is waived if you've been at the company > 1 year.
+
+**Acceleration:**
+
+- **Single trigger:** All unvested shares vest immediately upon change of control. Founder-friendly but rare; investors resist.
+- **Double trigger (standard):** Acceleration requires (a) change of control AND (b) involuntary termination of the founder within X months. Industry standard at Series A+.
+
+**Pushback:** "Double-trigger acceleration is industry standard. Without it, founders are exposed to acquirer post-acquisition staffing decisions."
+
+### Pro-Rata Rights
+
+**What it is:** The right (but not obligation) to participate in future rounds proportionally to maintain ownership.
+
+**Standard:** Lead investor + major investors (typically those above some ownership threshold) get pro-rata. Smaller checks often don't.
+
+**Founder impact:** Granting pro-rata is generally fine — it shows investor conviction and aligns long-term. The cost is small dilution in future rounds.
+
+**Pushback:** Only push back if there's a long tail of small investors each demanding pro-rata; cap to "major investors" defined by ownership %.
+
+### Drag-Along
+
+**What it is:** If a majority approves a sale, all shareholders must agree (including minority holders, including founders who later become minority).
+
+**Founder-friendly version:** Drag-along requires founder consent OR a minimum sale price threshold (e.g., > 3x liquidation preference).
+
+**Hostile version:** Drag-along with no founder consent and no price floor. Investors can force a sale at any price over founder objection.
+
+**Pushback:** "Drag-along is standard, but we need founder consent OR a price floor."
+
+### Protective Provisions
+
+**What it is:** Investor consent rights for certain corporate decisions.
+
+**Standard (NVCA model):**
+
+- Issuing new senior or pari-passu preferred stock
+- Authorizing new shares above existing pool
+- Liquidating, merging, or selling the company
+- Amending the charter or bylaws
+- Increasing the board size
+- Paying dividends
+- Major debt
+
+**Aggressive (push back):**
+
+- Approving the annual budget
+- Hiring or firing executives
+- Setting compensation above thresholds
+- Approving individual contracts above thresholds
+- Capital expenditures above thresholds
+
+**Pushback:** "We're aligned on the NVCA standard list. Operating decisions like budget and hiring are management's responsibility — protective provisions are for fundamental corporate changes."
+
+### Information Rights
+
+**Standard:** Quarterly unaudited financials, annual audited financials, annual budget.
+
+**Aggressive (push back):** Monthly financials, board observer rights, weekly KPI dashboards, inspection rights at will.
+
+**Pushback:** "Standard quarterly + annual is enough. Monthly creates significant CFO overhead at our stage. We'll commit to ad-hoc updates on material events."
+
+### Dividends
+
+**Standard:** None (default).
+
+**Acceptable:** Non-cumulative dividends "when and if declared by the board" — almost never paid in practice.
+
+**Hostile:** Cumulative dividends accrue every year regardless of declaration and must be paid in cash at exit. This is a creeping liquidation preference.
+
+**Pushback:** "Cumulative dividends create a hidden liquidation preference that accrues over time. Non-cumulative when-declared, or none, is standard."
+
+### Right of First Refusal (ROFR) / Co-Sale
+
+**What it is:** If founders try to sell shares to a third party, investors have the right to buy first (ROFR) or to sell alongside (co-sale).
+
+**Founder-friendly:** Standard ROFR + co-sale for all preferred; founders can still do secondary up to small thresholds without triggering.
+
+**Hostile:** No secondary at all without unanimous investor consent.
+
+**Pushback:** "We need to allow modest founder secondary (e.g., up to $1M aggregate) without investor consent — this is needed for founder financial planning."
+
+### Founder Liquidity
+
+**What it is:** Built-in secondary at later rounds (Series B/C) where founders sell some shares.
+
+**Standard:** Becoming more common; 10-20% of round size as founder secondary.
+
+**Pushback:** Raise this in Series B+ discussions; not typically negotiated at Series A.
+
+### Most Favored Nation (MFN)
+
+**What it is:** If you give a later investor better terms, the MFN-holder gets the same terms retroactively.
+
+**Common in:** Seed SAFEs and convertible notes; rare in priced rounds.
+
+**Founder trap:** MFN provisions can prevent you from offering competitive terms to new lead investors later. Be specific about what's covered (just SAFE terms? all terms?).
+
+### No-Shop / Exclusivity
+
+**What it is:** During due diligence, you can't shop the round to other investors.
+
+**Standard:** 30-45 days. Founder-friendly. Investor-aligned because it shows commitment.
+
+**Pushback only if:** > 60 days, or if it extends post-execution of definitive docs.
+
+---
+
+## Founder-Friendly Defaults (Cheat Sheet)
+
+| Clause | Founder-Friendly Default |
+|---|---|
+| Liquidation preference | 1x non-participating |
+| Anti-dilution | Broad-based weighted average |
+| Option pool | 8-12%, post-money |
+| Board (Series A) | 2F / 1I / 1Indep |
+| Vesting (founder re-vest) | 4yr / 1yr cliff, often with credit for time served |
+| Acceleration | Double-trigger |
+| Pro-rata | For lead + major investors |
+| Drag-along | Requires founder consent or price floor |
+| Protective provisions | NVCA standard list only |
+| Information rights | Quarterly + annual + budget |
+| Dividends | None or non-cumulative when-declared |
+| ROFR / co-sale | Standard, with carve-out for modest founder secondary |
+| MFN (in notes/SAFEs) | Avoid if possible; if not, narrow scope |
+| No-shop | 30-45 days |
+
+---
+
+## Negotiation Strategy
+
+**Pick your battles:** A term sheet has 25-40 clauses. Winning every one is impossible and signals you don't understand priorities.
+
+**Focus on the top 3 mistakes (in order):**
+
+1. Liquidation preference flavor (participating vs non-participating)
+2. Option pool pre-money vs post-money + size
+3. Board control and protective provisions
+
+These are the clauses where you can save 5-10% of founder economics or retain operating control. Everything else is secondary.
+
+**The "founder-friendly NVCA" framing:** Many investors signal their posture by deviating from the NVCA model (the industry standard documents published by the National Venture Capital Association). Pushing back to "let's use the NVCA standard" is rarely rejected and resolves most issues.
+
+**Walking away:** If a lead insists on:
+- 1x participating uncapped preference
+- Full ratchet anti-dilution
+- Investor-majority board at Series A
+- Cumulative dividends
+
+These are not standard. A founder-friendly lead doesn't insist on these. Either walk or get specific written justification (sometimes a distressed cap-table situation justifies one of them, but never all).
+
+---
+
+## After Signing
+
+Once the term sheet is signed:
+
+1. **No-shop is active.** Don't talk to other investors except to officially decline.
+2. **Definitive documents (SPA, IRA, Voting Agreement, ROFR Agreement) take 4-6 weeks.** Don't lose energy here; main fight was the term sheet.
+3. **Closing conditions:** legal opinion, secretary's certificate, charter filing, capitalization confirmation.
+4. **Wire timing:** Investors often wire 1-3 days after charter filing. Plan accordingly.
+
+Run `scripts/term_sheet_analyzer.py` on the structured JSON of the term sheet for an automated scoring + flag analysis.
+
+---
+
+**Final reminder:** This document is a decoder, not a negotiation manual. Real term sheet response always involves your venture / securities counsel + your lead investor's diligence + your board (if any). Use this as a primer before those conversations.

package/org-skills/git-advanced-workflows/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/git-advanced-workflows/SKILL.md

@@ -0,0 +1,203 @@
+---
+name: git-advanced-workflows
+description: "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues."
+tags: ["engineering","devops"]
+tools: []
+license: MIT
+source: https://github.com/wshobson/agents
+source_path: "plugins/developer-essentials/skills/git-advanced-workflows"
+source_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620
+---
+# Git Advanced Workflows
+
+Master advanced Git techniques to maintain clean history, collaborate effectively, and recover from any situation with confidence.
+
+## When to Use This Skill
+
+- Cleaning up commit history before merging
+- Applying specific commits across branches
+- Finding commits that introduced bugs
+- Working on multiple features simultaneously
+- Recovering from Git mistakes or lost commits
+- Managing complex branch workflows
+- Preparing clean PRs for review
+- Synchronizing diverged branches
+
+## Core Concepts
+
+### 1. Interactive Rebase
+
+Interactive rebase is the Swiss Army knife of Git history editing.
+
+**Common Operations:**
+
+- `pick`: Keep commit as-is
+- `reword`: Change commit message
+- `edit`: Amend commit content
+- `squash`: Combine with previous commit
+- `fixup`: Like squash but discard message
+- `drop`: Remove commit entirely
+
+**Basic Usage:**
+
+```bash
+# Rebase last 5 commits
+git rebase -i HEAD~5
+
+# Rebase all commits on current branch
+git rebase -i $(git merge-base HEAD main)
+
+# Rebase onto specific commit
+git rebase -i abc123
+```
+
+### 2. Cherry-Picking
+
+Apply specific commits from one branch to another without merging entire branches.
+
+```bash
+# Cherry-pick single commit
+git cherry-pick abc123
+
+# Cherry-pick range of commits (exclusive start)
+git cherry-pick abc123..def456
+
+# Cherry-pick without committing (stage changes only)
+git cherry-pick -n abc123
+
+# Cherry-pick and edit commit message
+git cherry-pick -e abc123
+```
+
+### 3. Git Bisect
+
+Binary search through commit history to find the commit that introduced a bug.
+
+```bash
+# Start bisect
+git bisect start
+
+# Mark current commit as bad
+git bisect bad
+
+# Mark known good commit
+git bisect good v1.0.0
+
+# Git will checkout middle commit - test it
+# Then mark as good or bad
+git bisect good  # or: git bisect bad
+
+# Continue until bug found
+# When done
+git bisect reset
+```
+
+**Automated Bisect:**
+
+```bash
+# Use script to test automatically
+git bisect start HEAD v1.0.0
+git bisect run ./test.sh
+
+# test.sh should exit 0 for good, 1-127 (except 125) for bad
+```
+
+### 4. Worktrees
+
+Work on multiple branches simultaneously without stashing or switching.
+
+```bash
+# List existing worktrees
+git worktree list
+
+# Add new worktree for feature branch
+git worktree add ../project-feature feature/new-feature
+
+# Add worktree and create new branch
+git worktree add -b bugfix/urgent ../project-hotfix main
+
+# Remove worktree
+git worktree remove ../project-feature
+
+# Prune stale worktrees
+git worktree prune
+```
+
+### 5. Reflog
+
+Your safety net - tracks all ref movements, even deleted commits.
+
+```bash
+# View reflog
+git reflog
+
+# View reflog for specific branch
+git reflog show feature/branch
+
+# Restore deleted commit
+git reflog
+# Find commit hash
+git checkout abc123
+git branch recovered-branch
+
+# Restore deleted branch
+git reflog
+git branch deleted-branch abc123
+```
+
+## Detailed patterns and worked examples
+
+Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
+
+## Best Practices
+
+1. **Always Use --force-with-lease**: Safer than --force, prevents overwriting others' work
+2. **Rebase Only Local Commits**: Don't rebase commits that have been pushed and shared
+3. **Descriptive Commit Messages**: Future you will thank present you
+4. **Atomic Commits**: Each commit should be a single logical change
+5. **Test Before Force Push**: Ensure history rewrite didn't break anything
+6. **Keep Reflog Aware**: Remember reflog is your safety net for 90 days
+7. **Branch Before Risky Operations**: Create backup branch before complex rebases
+
+```bash
+# Safe force push
+git push --force-with-lease origin feature/branch
+
+# Create backup before risky operation
+git branch backup-branch
+git rebase -i main
+# If something goes wrong
+git reset --hard backup-branch
+```
+
+## Common Pitfalls
+
+- **Rebasing Public Branches**: Causes history conflicts for collaborators
+- **Force Pushing Without Lease**: Can overwrite teammate's work
+- **Losing Work in Rebase**: Resolve conflicts carefully, test after rebase
+- **Forgetting Worktree Cleanup**: Orphaned worktrees consume disk space
+- **Not Backing Up Before Experiment**: Always create safety branch
+- **Bisect on Dirty Working Directory**: Commit or stash before bisecting
+
+## Recovery Commands
+
+```bash
+# Abort operations in progress
+git rebase --abort
+git merge --abort
+git cherry-pick --abort
+git bisect reset
+
+# Restore file to version from specific commit
+git restore --source=abc123 path/to/file
+
+# Undo last commit but keep changes
+git reset --soft HEAD^
+
+# Undo last commit and discard changes
+git reset --hard HEAD^
+
+# Recover deleted branch (within 90 days)
+git reflog
+git branch recovered-branch abc123
+```

package/org-skills/git-advanced-workflows/references/details.md

@@ -0,0 +1,203 @@
+# git-advanced-workflows — detailed patterns and worked examples
+
+## Practical Workflows
+
+### Workflow 1: Clean Up Feature Branch Before PR
+
+```bash
+# Start with feature branch
+git checkout feature/user-auth
+
+# Interactive rebase to clean history
+git rebase -i main
+
+# Example rebase operations:
+# - Squash "fix typo" commits
+# - Reword commit messages for clarity
+# - Reorder commits logically
+# - Drop unnecessary commits
+
+# Force push cleaned branch (safe if no one else is using it)
+git push --force-with-lease origin feature/user-auth
+```
+
+### Workflow 2: Apply Hotfix to Multiple Releases
+
+```bash
+# Create fix on main
+git checkout main
+git commit -m "fix: critical security patch"
+
+# Apply to release branches
+git checkout release/2.0
+git cherry-pick abc123
+
+git checkout release/1.9
+git cherry-pick abc123
+
+# Handle conflicts if they arise
+git cherry-pick --continue
+# or
+git cherry-pick --abort
+```
+
+### Workflow 3: Find Bug Introduction
+
+```bash
+# Start bisect
+git bisect start
+git bisect bad HEAD
+git bisect good v2.1.0
+
+# Git checks out middle commit - run tests
+npm test
+
+# If tests fail
+git bisect bad
+
+# If tests pass
+git bisect good
+
+# Git will automatically checkout next commit to test
+# Repeat until bug found
+
+# Automated version
+git bisect start HEAD v2.1.0
+git bisect run npm test
+```
+
+### Workflow 4: Multi-Branch Development
+
+```bash
+# Main project directory
+cd ~/projects/myapp
+
+# Create worktree for urgent bugfix
+git worktree add ../myapp-hotfix hotfix/critical-bug
+
+# Work on hotfix in separate directory
+cd ../myapp-hotfix
+# Make changes, commit
+git commit -m "fix: resolve critical bug"
+git push origin hotfix/critical-bug
+
+# Return to main work without interruption
+cd ~/projects/myapp
+git fetch origin
+git cherry-pick hotfix/critical-bug
+
+# Clean up when done
+git worktree remove ../myapp-hotfix
+```
+
+### Workflow 5: Recover from Mistakes
+
+```bash
+# Accidentally reset to wrong commit
+git reset --hard HEAD~5  # Oh no!
+
+# Use reflog to find lost commits
+git reflog
+# Output shows:
+# abc123 HEAD@{0}: reset: moving to HEAD~5
+# def456 HEAD@{1}: commit: my important changes
+
+# Recover lost commits
+git reset --hard def456
+
+# Or create branch from lost commit
+git branch recovery def456
+```
+
+## Advanced Techniques
+
+### Rebase vs Merge Strategy
+
+**When to Rebase:**
+
+- Cleaning up local commits before pushing
+- Keeping feature branch up-to-date with main
+- Creating linear history for easier review
+
+**When to Merge:**
+
+- Integrating completed features into main
+- Preserving exact history of collaboration
+- Public branches used by others
+
+```bash
+# Update feature branch with main changes (rebase)
+git checkout feature/my-feature
+git fetch origin
+git rebase origin/main
+
+# Handle conflicts
+git status
+# Fix conflicts in files
+git add .
+git rebase --continue
+
+# Or merge instead
+git merge origin/main
+```
+
+### Autosquash Workflow
+
+Automatically squash fixup commits during rebase.
+
+```bash
+# Make initial commit
+git commit -m "feat: add user authentication"
+
+# Later, fix something in that commit
+# Stage changes
+git commit --fixup HEAD  # or specify commit hash
+
+# Make more changes
+git commit --fixup abc123
+
+# Rebase with autosquash
+git rebase -i --autosquash main
+
+# Git automatically marks fixup commits
+```
+
+### Split Commit
+
+Break one commit into multiple logical commits.
+
+```bash
+# Start interactive rebase
+git rebase -i HEAD~3
+
+# Mark commit to split with 'edit'
+# Git will stop at that commit
+
+# Reset commit but keep changes
+git reset HEAD^
+
+# Stage and commit in logical chunks
+git add file1.py
+git commit -m "feat: add validation"
+
+git add file2.py
+git commit -m "feat: add error handling"
+
+# Continue rebase
+git rebase --continue
+```
+
+### Partial Cherry-Pick
+
+Cherry-pick only specific files from a commit.
+
+```bash
+# Show files in commit
+git show --name-only abc123
+
+# Checkout specific files from commit
+git checkout abc123 -- path/to/file1.py path/to/file2.py
+
+# Stage and commit
+git commit -m "cherry-pick: apply specific changes from abc123"
+```

package/org-skills/git-workflow/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Affaan Mustafa
+
+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.