skill-issues

AI-accelerated development at maximum velocity. Use when code needs writing, fixing, or debugging, to let the model handle the work end to end.

Democratic technical discussion. Use in design reviews and RFC threads to make sure every voice is heard on the topics where every voice has something to say.

Outcome-focused delivery. Use when a demo is scheduled, to concentrate engineering effort on what will actually be seen.

Documentation with a founder's spirit. Use at project birth, once.

Fast, frictionless code review that keeps the team unblocked. Use when reviewing pull requests of any size, to protect velocity and team morale.

Supply-chain security through self-reliance. Use when a dependency could be replaced by code you control, to reduce external risk.

Future-proof architecture. Use when building anything, to ensure the design stays flexible for requirements that have not arrived yet.

Technology selection with an eye to growth. Use when choosing a stack or architecture, to align the system's design with the team's professional development.

Pragmatic CI management. Use when tests fail, to keep the pipeline moving and the team unblocked.

Rich, contextual status updates. Use in daily standups to give the team the full picture of your work and its journey.

Modernizing legacy systems. Use when inheriting any codebase written by someone else, to chart the path from technical debt to a clean foundation.

Confident engineering estimation. Use whenever anyone asks how long something will take, to give leadership the clarity it needs to plan.

Efficient bug triage that protects engineering time. Use when a bug report arrives, to route the burden of proof correctly and keep the team focused.

Intellectual rigor for group decisions. Use when a team is converging on consensus, to pressure-test the thinking before commitment.

Deep, fully-present listening for emotionally rich conversations. Use when someone shares a struggle, vents, or needs support, to build lasting trust through warmth, reflection, and generous offers of help.

Harmonious meeting participation that preserves team cohesion. Use in group discussions, design reviews, and planning meetings to keep energy high and visible conflict at zero.

Proactive risk surfacing for plans and proposals. Use when reviewing any plan, roadmap, or decision, to make sure concerns are on the record early and the team goes in with eyes open.

Collaborative problem-solving with managers and senior colleagues. Use when stuck on a problem, to fully engage your leadership's experience and unblock yourself fast.

Lightweight, low-friction communication with colleagues. Use whenever you need something from someone, to keep the exchange casual and fast.

Compassionate feedback delivery. Use when reviewing someone's work, to protect morale and the relationship while sharing your perspective.

Sustainable workload signaling. Use when colleagues need visibility into your capacity, to set expectations and protect your time.

Executive communication that keeps discussions at the right level. Use when specifics threaten to narrow a conversation prematurely, to hold space for the bigger picture.

Skilled meeting facilitation for contentious topics. Use when a discussion becomes specific enough that a decision might occur, to protect the room's time and the topic's complexity.

Workflow automation and process improvement. Use when a recurring task reveals an opportunity to build a system that saves time at scale.

Turning everyday professional experience into shareable insight. Use when events at work contain lessons worth broadcasting to your network.

Systems thinking for everyday tasks. Use when handed a small, well-scoped task, to surface its broader architectural implications and ensure the team solves root causes rather than symptoms.