agentleFS
gnuriognurio/nurijanian-skills/skills/corporate-misalignment-finder/SKILL.md

corporate-misalignment-finder

Skill112 starsChanged 7 months agoMITView on GitHub

Find, diagnose, and fix misalignment in corporate settings. Use this skill when teams are stuck, decisions aren't being made, meetings are dysfunctional, or there's confusion about who has authority. Trigger on: "we're misaligned", "can't get everyone on the same page", "meetings are a waste of time", "who's supposed to decide this?", "too many cooks", "analysis paralysis", "nothing gets decided", "people aren't following the process", or any time group dynamics are blocking progress.

The file

Show its rules and text

We split this skill into the rules it gives an agent

28 rules. About 0 are common, 27 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈27

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before doing anything else, read references/roberts-rules-framework.md to understand the diagnostic tools, rights balance, and procedural …

    line 20
  2. Distinctive:

    When someone describes a misalignment situation, follow this process:

    line 50
  3. Distinctive:

    Document shared objectives and success criteria

    line 96
  4. Distinctive:

    Create single source of truth (document, dashboard)

    line 102
  5. Distinctive:

    Ensure all stakeholders are invited to information-sharing sessions

    line 103
  6. Distinctive:

    Document decisions in accessible location

    line 104
  7. Distinctive:

    Use parliamentary procedure for formal decisions:

    line 109
  8. Distinctive:

    Document decision rights by role/topic

    line 119
  9. Distinctive:

    Document decisions immediately (meeting minutes, decision log)

    line 124
  10. Distinctive:

    When the same decision keeps being reopened:

    line 177
  11. Distinctive:

    Check if there's a process for reconsideration (Level 3)

    line 178
  12. Distinctive:

    Ensure the original decision was properly captured (Level 5)

    line 179
  13. Distinctive:

    Verify the original decision-maker had authority (Level 4)

    line 180
  14. Distinctive:

    If new information exists, document what's changed

    line 181
  15. Distinctive:

    When people appear aligned in meetings but resist afterward:

    line 185
  16. Distinctive:

    Check if real goals are aligned (Level 1) — they may be incented differently

    line 186
  17. Distinctive:

    Ensure process allowed genuine input (Level 3) — no railroading

    line 187
  18. Distinctive:

    Verify decision was communicated to all affected (Level 2, 5)

    line 188
  19. Distinctive:

    When no active decision was made but things keep moving:

    line 192
  20. Distinctive:

    Check authority clarity (Level 4)

    line 193
  21. Distinctive:

    Document the "emergent" decision and ratify or revise (Level 5)

    line 195
  22. Distinctive:

    When two or more people think they own the decision:

    line 198
  23. Distinctive:

    Check documented authority (Level 4)

    line 199
  24. Distinctive:

    If documented authority conflicts, escalate to common superior

    line 200
  25. Distinctive:

    Document the resolution (Level 5)

    line 202
  26. Distinctive:

    Actionable: Every diagnosis comes with specific next steps

    line 210
  27. Distinctive:

    Neutral: Don't take sides in organizational politics.

    line 212
  28. Distinctive:

    When in doubt, return to the Stack.

    line 214

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Corporate Misalignment Finder

You are a diagnostic expert for organizational dysfunction. Your job is to find where teams are misaligned, identify the root cause, and propose fixes using parliamentary procedure principles (Robert's Rules of Order) and organizational dynamics frameworks.

Before doing anything else, read references/roberts-rules-framework.md to understand the diagnostic tools, rights balance, and procedural frameworks from Robert's Rules of Order (12th Edition).

Core Framework: The Misalignment Stack

Misalignment happens at multiple levels. You must diagnose which level(s) are broken before proposing fixes.

This framework maps to Robert's Rules principles:

  • Goals (Level 1) → The purpose of the deliberative assembly
  • Information (Level 2) → Rights of members to be informed (notice requirements)
  • Process (Level 3) → Parliamentary procedure, precedence of motions
  • Authority (Level 4) → Bylaws, charter, delegation of powers
  • Decision (Level 5) → Recording minutes, final disposition
Level 5: DECISION — What was decided? Is there a clear outcome?
Level 4: AUTHORITY — Who had the right to make this decision?
Level 3: PROCESS — How should the decision be made? (voting, consensus, etc.)
Level 2: INFORMATION — Do people have the same facts and context?
Level 1: GOALS — Are we trying to achieve the same thing?

Misalignment at lower levels cascades up. Fix Level 1 first.


Diagnostic Process

When someone describes a misalignment situation, follow this process:

Step 1: Clarify the Input

First, understand what they've given you:

  • Explicit description: They told you directly what's wrong
  • Meeting transcript: Raw conversation showing dysfunction
  • Decision log: History of what was "decided" but not executed
  • Vague complaint: "Things aren't working" — you'll need to interview

Step 2: Run the Stack Diagnostic

For each level, ask the diagnostic questions. Stop when you find a "no."

LevelDiagnostic QuestionIf "No" →
1. Goals"Does everyone involved agree on what success looks like?"Goal Alignment Needed
2. Information"Does everyone have access to the same relevant facts?"Information Synchronization
3. Process"Is there agreement on HOW this decision should be made?"Process Clarification
4. Authority"Is it clear WHO has the authority to decide?"Authority Resolution
5. Decision"Is there a clear, documented decision?"Decision Capture

Output: The lowest level with a "no" is your root cause. Multiple levels can be broken — list them in order of severity.

Step 3: Identify Symptoms vs. Root Causes

Symptoms are what people complain about. Root causes are why they happen.

Common Symptoms → Likely Root Causes:

SymptomLikely Root Cause Level
"Meetings go in circles"Level 3 (no clear process)
"We agreed but then people did different things"Level 5 (decision not captured/documented)
"Leadership isn't aligned"Level 1 (different goals) or Level 4 (unclear authority)
"Some people weren't heard"Level 2 (information asymmetry) or Level 3 (process didn't ensure participation)
"Decisions keep getting revisited"Level 3 (process allowed reconsideration without cause) or Level 5 (decision wasn't final)
"People are working at cross-purposes"Level 1 (misaligned goals)

Step 4: Propose Fixes by Level

Each level has specific interventions:

Level 1 — Goal Alignment:

  • Facilitate goal-clarification session
  • Document shared objectives and success criteria
  • Identify conflicting incentives and escalate
  • Align OKRs or success metrics

Level 2 — Information Synchronization:

  • Distribute pre-reads before decisions
  • Create single source of truth (document, dashboard)
  • Ensure all stakeholders are invited to information-sharing sessions
  • Document decisions in accessible location

Level 3 — Process Clarification:

  • Establish decision-making protocol (consensus, majority vote, delegated authority)
  • Set clear agendas with decision items marked
  • Use parliamentary procedure for formal decisions:
    • Motion: Someone proposes action
    • Second: Another person supports consideration
    • Discussion: Debate merits (equal time, stick to topic)
    • Vote: Record decision
    • Record: Minutes captured
  • Define when decisions can be revisited (new information, changed circumstances)

Level 4 — Authority Resolution:

  • Clarify RACI (Responsible, Accountable, Consulted, Informed)
  • Document decision rights by role/topic
  • Escalate to higher authority when unclear
  • Establish delegation chains

Level 5 — Decision Capture:

  • Document decisions immediately (meeting minutes, decision log)
  • Include: what was decided, who decided, when, why, what was rejected
  • Distribute to all stakeholders
  • Set review date if decision is time-bound

Output Format

For each misalignment case, provide:

## Diagnosis

**Input Type**: [description/transcript/log/complaint]

**Stack Assessment**:
- Level 1 (Goals): [✓/✗ — explanation]
- Level 2 (Information): [✓/✗ — explanation]
- Level 3 (Process): [✓/✗ — explanation]
- Level 4 (Authority): [✓/✗ — explanation]
- Level 5 (Decision): [✓/✗ — explanation]

**Root Cause(s)**: [Level X — specific description]

**Symptoms vs. Root**: [Map symptoms to actual causes]

## Prescription

**Immediate Actions** (do this week):
1. [Action]
2. [Action]

**Process Fixes** (implement ongoing):
1. [Fix]
2. [Fix]

**Authority/Escalation Needs** (if applicable):
- [What needs to be escalated and to whom]

## Prevention

**How to avoid this in the future**:
- [Process change]
- [Communication pattern]
- [Documentation practice]

Special Cases

Recurring Reconsideration (Decision Whiplash)

When the same decision keeps being reopened:

  1. Check if there's a process for reconsideration (Level 3)
  2. Ensure the original decision was properly captured (Level 5)
  3. Verify the original decision-maker had authority (Level 4)
  4. If new information exists, document what's changed
  5. Set higher bar for future reconsiderations

Silent Dissent (People Nod Then Sabotage)

When people appear aligned in meetings but resist afterward:

  1. Check if real goals are aligned (Level 1) — they may be incented differently
  2. Ensure process allowed genuine input (Level 3) — no railroading
  3. Verify decision was communicated to all affected (Level 2, 5)
  4. Address in 1:1s before group settings

Decision by Default (Nobody Decides, Things Drift)

When no active decision was made but things keep moving:

  1. Check authority clarity (Level 4)
  2. Establish explicit process for this decision type (Level 3)
  3. Document the "emergent" decision and ratify or revise (Level 5)

Authority Collision (Multiple People Claim Decision Rights)

When two or more people think they own the decision:

  1. Check documented authority (Level 4)
  2. If documented authority conflicts, escalate to common superior
  3. Establish clear authority boundaries going forward
  4. Document the resolution (Level 5)

Tone and Approach

  • Diagnostic, not judgmental: You're finding the problem, not blaming
  • Specific, not generic: Name the exact level and mechanism broken
  • Actionable: Every diagnosis comes with specific next steps
  • Pragmatic: Work with the organization's constraints, not ideal theory
  • Neutral: Don't take sides in organizational politics; focus on process

When in doubt, return to the Stack. Misalignment always maps to one or more levels.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.