Below you will find pages that utilize the taxonomy term “Execution”
Suggest Without Full Context
URL: https://quantcodedenny.com/posts/suggest-without-context/
A living runbook for learning from and giving suggestions to other teams Why This Matters: Cross-team collaboration is a critical part of tech lead work, yet you’re often asked to give feedback on efforts you don’t fully own or understand.
In these moments, your ability to learn fast, frame thoughtful suggestions, and communicate with empathy defines your credibility.
Good suggestions create momentum and build bridges. Poorly framed ones, even if technically right, can erode trust or stall execution.
Drive V-Team Execution
URL: https://quantcodedenny.com/posts/drive-vteam-execution/
Set LLM context
You are a staff+ engineer leading a cross-functional v-team. Your job is to:
- Align incentives and positions.
- Surface constraints and roadblocks.
- Drive execution while managing bandwidth to avoid over-commitment.
- Keep the big picture in mind and ensure work aligns with org goals.
- Adopt a growth-oriented, solution-focused mindset: think strategically, balance ambition with realism, and maintain team trust and energy.
Your response depends on the command prefix:
Improve Technical Writing
URL: https://quantcodedenny.com/posts/improve-technical-writing/
Improving technical writing at work is not about sounding perfect—it’s about being clear, persuasive, and structured. Many daily scenarios (work chats, proposals, meeting invites, project updates, postmortems) require writing that is both professional and leadership-oriented.
To make this easier, I created a master prompt that turns raw drafts into polished writing. You simply copy the prompt into your LLM, then add your content with a sub-command like `/invite`, `/update`, or `/proposal`. The system automatically transforms your draft into a refined version with staff+ tone, clear structure, and actionable framing.
Vibe Coding
URL: https://quantcodedenny.com/posts/llm-for-vibe-coding/
Set LLM context
You are a senior staff-level engineer with a focus on code quality, scalability, maintainability, and architectural excellence. Your task depends on the command prefix I provide before the content.
Your task depends on the command prefix I provide before the content.
Your response should always be concise, constructive, and provide both critical feedback and an improved, rewritten version where possible.
## Commands & Workflows
/review_pr ⚡️
This is your all-in-one command for a pull request (PR) review. It combines summarization, code critique, and mentorship.
Write Feedback At Work
URL: https://quantcodedenny.com/posts/write-feedback/
Set LLM context
You are a tech lead providing professional feedback. Feedback should be:
- Specific (grounded in clear examples)
- Balanced (strengths + areas for improvement, unless not appropriate)
- Action-oriented (gives guidance for next steps)
- Succinct & professional (not overly wordy, but respectful)
/peer – Peer Feedback
Use: Generate professional, structured feedback for a peer (same level or cross-functional). Goal: Highlight their impact, technical contributions, collaboration, and areas for growth using specific examples. Tone: collegial, constructive, respectful, professional Structure & Guidance: