sethdford/claude-skills - Page 10

hiring-interview-design

Design interview processes that assess actual capability, reduce bias, and provide good candidate experience. Use when building hiring practices or expanding the team.

retrospective-facilitation-tl

Facilitate effective retrospectives that surface real issues, drive action, and build psychological safety. Use at sprint end or after major initiatives.

team-charter

Create a team charter that documents team purpose, values, norms, and decision-making processes. Use when forming team or clarifying culture.

team-health-check

Conduct team health assessments to identify morale, skill, process, and engagement issues before they become crises. Use quarterly or when noticing team friction.

tech-lead-journal

Maintain a personal journal for reflection, decision-making documentation, and organizational memory. Use for continuous learning and calibrating leadership effectiveness.

tech-talk-preparation

Prepare and deliver technical talks that educate, inspire, and represent your team and company. Use for conferences, internal knowledge sharing, or building credibility.

build-vs-buy-analysis

Systematically evaluate whether to build custom solutions or buy/adopt existing products. Use when facing major make-or-buy decisions on infrastructure, tooling, or features.

decision-matrix

Use weighted criteria matrices to systematically compare options and make defensible technical decisions. Use when evaluating competing approaches or vendors.

post-decision-review

Conduct retrospective reviews of major decisions 3-6 months after implementation to capture learnings and calibrate future decisions. Use to build institutional memory and improve decision quality.

proof-of-concept-criteria

Define when and how to validate ideas through PoCs before full implementation. Use to decide between spikes, PoCs, and production rollouts.

rfc-process

Structure Request for Comments processes to document major technical decisions, surface concerns, and build consensus. Use before implementing significant architectural changes.

risk-mitigation-plan

Identify risks in major decisions and plan mitigation strategies before they become emergencies. Use when implementing architectural changes or making irreversible decisions.

spike-plan

Design research spikes to investigate technical uncertainty before committing to large implementation efforts. Use when feasibility is unclear or approach is unproven.

technology-evaluation

Build evaluation frameworks for selecting technologies, frameworks, or vendors using consistent criteria. Use when choosing dependencies, platforms, or major tooling.

capacity-planning

Model team capacity across quarters, accounting for hiring, attrition, and project work. Use when forecasting resource availability for roadmaps.

dependency-mapping

Identify and visualize dependencies between teams, systems, and work items to prevent blocked work. Use when planning cross-team initiatives.

estimation-techniques

Apply evidence-based estimation methods (story points, t-shirt sizing, planning poker) to reduce uncertainty. Use when sizing work for sprints or releases.

risk-register

Systematically identify and track technical and organizational risks that could impact delivery timelines. Use when planning significant initiatives.

sprint-planning-guide

Facilitate effective sprint planning meetings that balance team capacity, business priorities, and technical health. Use when preparing for sprint planning.

technical-debt-prioritization

Evaluate and prioritize technical debt to balance feature velocity with system health. Use when deciding what debt to address in upcoming sprints.

technical-roadmap

Build multi-quarter technical roadmaps aligned with business goals, clearly showing strategic investments, trade-offs, and dependencies. Use when planning longer-term technical direction, communicating with stakeholders, or aligning engineering capacity with…

velocity-analysis

Track and interpret sprint velocity to forecast capacity, identify bottlenecks, and improve planning accuracy. Use when analyzing team productivity trends.

work-breakdown-structure

Decompose complex initiatives into manageable work items with clear ownership and milestones. Use when planning large features or multi-team projects.