engineering-culture
Installation
SKILL.md
Engineering Culture
Scope
Covers
- Diagnosing the current engineering culture and delivery system (technical, architectural, cultural, and management capabilities)
- Defining a clear engineering culture code (principles → behaviors → decision rules → anti-patterns)
- Aligning org structure with architecture (Conway’s Law) and reducing cross-team friction
- Increasing clock speed (safe shipping + experimentation throughput) and improving DevEx
- Creating a practical cross-functional workflow contract (how engineering + PM/Design/Marketing collaborate in the same toolchain)
- Making AI-assisted development safe and effective (humans as “architects”: spec, review, and oversight)
When to use
- “Help me improve engineering culture / DevEx and make it concrete.”
- “Our delivery is slow—build a plan to increase shipping speed without breaking things.”
- “Our org structure fights our architecture—analyze Conway’s Law and propose changes.”
- “We want tighter processes and faster experimentation (higher clock speed).”
- “Non-engineering functions struggle to work with engineering—define a shared workflow contract.”
- “We’re adopting AI coding tools/agents—set norms so engineers shift toward higher-level design and review.”
Related skills
More from liqiongyu/lenny_skills_plus
problem-definition
Define a product problem: problem statement, JTBD, alternatives, evidence, metrics. See also: writing-prds (solution spec).
13giving-presentations
Plan and deliver presentations: brief, narrative, slide outline, Q&A bank, rehearsal plan. See also: written-communication (async writing).
13competitive-analysis
Produce a Competitive Analysis Pack (alternatives map, landscape, battlecards, monitoring plan).
11pricing-strategy
Create a Pricing Strategy Pack (value metric, packaging, price points, conversion mechanics, rollout).
11startup-ideation
Generate and evaluate startup ideas: theses table, scorecard, top idea brief, validation plan. See also: startup-pivoting (existing product).
11writing-prds
Write a decision-ready PRD for cross-functional alignment. See also: writing-specs-designs (build-ready spec).
11