software-engineering-eng-chief

Triage engineering requests and route them to specialized experts for documented decisions.

Updated May 6, 2025
One-click install
npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill software-engineering-eng-chief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-engineering-eng-chief
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/software-engineering/eng-chief
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill software-engineering-eng-chief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves ambiguous engineering requests by routing work to the right specialists, coordinating multi-agent workflows, and producing documented, evidence-based decisions.

Core Features & Use Cases

  • Request triage and specialist routing: Classifies inputs by category, urgency, and scope, then dispatches the right subset of engineering experts (architecture, code quality, DevOps, security, data, performance).
  • Multi-agent workflow orchestration: Runs predefined end-to-end flows such as system design, PR/code review, incident response, and tech-debt reduction.
  • Conflict resolution with decision protocol: When experts disagree, applies a structured trade-off and evidence check, then records the outcome in ADR form.

Use case example: When planning a greenfield service, it can orchestrate domain modeling, architecture and API design, security threat modeling, CI/CD and ops planning, distributed-system considerations, and finish with a cross-cutting quality gate and sign-off.

Quick Start

Ask: "Triage my engineering request to build a new service from scratch and produce an evidence-based execution plan with the right ADR decision points."

Frequently Asked Questions about software-engineering-eng-chief

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

FAQPage Schema
How do I orchestrate multi-agent workflows for engineering decisions?

Multi-agent workflow orchestration triages engineering requests by category, urgency, and scope, then routes them to specialized experts in architecture, DevOps, or security to produce documented decisions. It coordinates agents across system design, PR review, and incident response workflows.

What is the best way to resolve technical conflicts between engineering experts?

Technical conflict resolution applies a structured trade-off and evidence check protocol when specialists disagree during engineering orchestration. This decision protocol evaluates conflicting expert outputs, resolves disputes using evidence-based criteria, and records the final outcome in ADR form.

How do I document technical decision making with ADRs?

Document technical decision making by consolidating multi-agent workflow outputs into Architecture Decision Records. The orchestration process captures evidence-based trade-offs, conflict resolutions, and fitness functions, producing actionable ADRs that satisfy deterministic workflow execution requirements.

Can I route engineering requests to specialized specialists automatically?

Request triage and specialist routing classifies engineering inputs by category, urgency, and scope, then dispatches work to the right subset of experts across architecture, code quality, DevOps, security, data, and performance domains for coordinated problem-solving.

Does engineering orchestration support incident response and tech-debt reduction?

Engineering orchestration supports predefined end-to-end workflows including incident response, tech-debt reduction, system design, and PR code review. These multi-agent flows coordinate specialized experts and apply cross-cutting quality gates to produce evidence-based execution plans.

When do I need engineering orchestration for system design?

Engineering orchestration is needed for system design when planning greenfield services that require coordinating domain modeling, architecture, API design, security threat modeling, CI/CD planning, and distributed-system considerations into a unified execution plan with ADR decision points.