eng-quality-handoff
Collaborative Quality Handoff
Intent
- Make it effortless for reviewers, QA, and partners to understand, validate, and extend your work.
- Ensure ownership persists after merge via clear action items and shared context.
Workflow
- Narrate the change
- Summarize problem, approach, and tradeoffs in the PR/issue using concise bullets.
- Link related tickets, specs, dashboards, or smart-contract addresses.
- Surface review focus
- Call out risky areas, migrations, or TODOs explicitly; request specific expertise if needed.
- Attach evidence
- Provide test results, captures, or transaction hashes inline so reviewers don’t need to rerun everything.
- Plan follow-ups
- Create tasks for deferred work, debt, or experiment cleanups with owners and timelines.
- Stay available
- Monitor review threads, CI pipelines, and post-merge telemetry; respond quickly and document resolutions.
Verification
- Review checklist complete (tests attached, docs/flags updated, reviewers assigned).
- Outstanding issues tracked with owners; no “known issue” left implicit.
- After merge, confirm deployment/monitoring links are shared with relevant teams.
More from tjboudreaux/cc-plugin-engineering-excellence
eng-tdd
Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
2eng-verification
Mandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.
2eng-performance
Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.
2eng-user-impact
Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
2meta-superpowers
Startup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.).
2eng-observability
Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.
2