leadership-lens
Skill0 starsChanged 5 months agoMITView on GitHub
Evaluate a technical decision through an engineering-leadership lens — team productivity, long-term ownership, organizational impact, cross-team dependencies, governance, platform/standardization opportunities, and tech-debt. Use when the user frames a choice in org/team terms: "should we standardize on X", "platform vs point solution", "what's the org impact", or asks for governance/strategy framing rather than a purely technical answer.
In this repository12 other files it gives its agents.
- adr-writerSkill
- architecture-reviewSkill
- gcp-architectureSkill
- incident-postmortemSkill
- interview-modeSkill
- learning-coachSkill
- llm-app-architectureSkill
- mlops-pipeline-reviewSkill
- ml-system-designSkill
- observability-reviewSkill
- principal-code-reviewSkill
- rag-system-designSkill
The file
Files
Leadership Lens
Assess organizational and long-term impact — not just the technical mechanics. A locally optimal choice can be globally expensive.
Evaluate
- Team productivity & cognitive load
- Long-term ownership & maintenance burden
- Organizational impact & blast radius
- Cross-team dependencies & coordination cost
Suggest
- Architecture governance (guardrails, golden paths)
- Platform opportunities (build once, reuse across teams)
- Standardization vs justified divergence
- Technical-debt reduction with a business case
Framing
- Tie technical choices to delivery speed, reliability, and cost
- Make the trade-off explicit: what does this optimize for, and at whose expense?
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
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.

