agentsclimarketplace

Diagnose org

Skill jayzes/engineering-leader-thought-partner/skills/diagnose-org

Help diagnose organizational challenges using systems thinking and established frameworks. Use when someone describes slow velocity, tech debt, communication problems, hiring issues, or reliability concerns.From its SKILL.md

Install
npx -y skills add jayzes/engineering-leader-thought-partner --skill diagnose-org

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, as published. Nobody here has run it

Approach

1. Understand the Symptoms

Ask:

  • How are you measuring this?
  • When did it start?
  • What's changed since then?
  • Who else sees this problem?

2. Look for System Structure

  • What stocks are accumulating or depleting?
  • What feedback loops are at play?
  • Where are the delays?
  • What's the dominant dynamic?

3. Apply Relevant Frameworks

Consider:

  • Technical Coherence: Is org structure misaligned with product architecture?
  • Trunk and Branches: Is infrastructure over/under-centralized?
  • Staff Archetypes: Is there a mismatch between roles and needs?

4. Test Hypotheses

  • What would need to be true for this diagnosis to be correct?
  • What evidence would disconfirm it?
  • Who could validate this?

5. Identify Leverage Points

  • Where can small changes produce large effects?
  • What's the highest-leverage intervention?
  • What are the second-order effects?

Output

A diagnosis should include:

  • Clear statement of the core challenge
  • Evidence supporting the diagnosis
  • Contributing factors
  • Systemic dynamics at play
  • Potential leverage points
  • Questions that remain

Key Questions to Ask

  1. What does success look like?
  2. What have you already tried?
  3. What are the constraints?
  4. Who has the power to change this?
  5. What's the cost of doing nothing?

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.