senior-engineer

Produce architecture reviews, refactoring plans, and ADR recommendations with severity-labelled feedback.

7|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/pranav8494/team-of-agents --skill senior-engineer-pranav8494
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-engineer
Source: https://github.com/pranav8494/team-of-agents/tree/main/skills/senior-engineer
Command: npx skills add https://github.com/pranav8494/team-of-agents --skill senior-engineer-pranav8494

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review and design complex software changes by clarifying trade-offs, improving correctness and quality, and documenting the rationale so decisions last.

Core Features & Use Cases

  • Architecture and code review: Deliver ADR-format recommendations and per-issue feedback with severity labels, including security, observability, and test gaps.
  • Refactoring and system decomposition: Propose safe, incremental refactoring plans and bounded-context/service boundary strategies with failure-mode awareness.
  • Technical design and mentoring: Produce design documents, structured trade-off evaluations, and engineering explanations grounded in established principles and patterns.

Quick Start

Ask for an architecture decision or code review by telling the AI what system you’re changing and what outcome you need, for example: Review my backend service design for scalability and correctness, propose two or three options, and end with an ADR-style recommendation.

Frequently Asked Questions about senior-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an architecture decision record for a complex system decomposition?

Architecture decision records (ADRs) document design rationale by clarifying trade-offs, proposing bounded-context strategies, and ensuring decisions last. You produce ADR-format recommendations with explicit failure-mode awareness and incremental refactoring plans.

What is the best way to perform a security review and critic pass on backend service design?

A security review evaluates your backend design by delivering per-issue feedback with severity labels, identifying observability gaps, and applying safety checks. It combines specialist findings into a structured critic pass for correctness and quality.

How do I plan a safe refactoring strategy using SOLID and DDD principles?

Refactoring with SOLID and DDD principles involves proposing safe, incremental refactoring plans and bounded-context service boundary strategies. This approach ensures system decomposition maintains structural integrity while evaluating established patterns and trade-offs.

Can I use this approach to review technical design documents and evaluate engineering trade-offs?

Reviewing technical design documents requires structured trade-off evaluations and engineering explanations grounded in established principles. You produce design documents with explicit trade-offs, severity-labelled feedback, and an end response confidence signal.

When do I need a formal test strategy plan for scalable architecture changes?

A formal test strategy plan is needed when making scalable architecture changes to identify test gaps and ensure safety. It applies severity-labelled feedback and failure-mode awareness to validate system correctness before implementation.

What are the limitations of relying on automated code review for system decomposition?

Automated code review limitations include missing nuanced domain context and architectural trade-offs. Structured deliverables with severity-labelled feedback and explicit SOLID/DDD principles ensure refactoring safety that purely automated approaches cannot guarantee.