Architecture Research Report

Research a technical question deeply, then produce an evidence-dense architecture report that takes a position, shows its work, and carries Mermaid diagrams and comparison tables. Writes as a solution/systems architect and senior AI/data engineer would: leads with the finding, grounds every claim in a citable source (file:line, benchmark number, doc §-reference), costs the recommendation, claims the negative space, and names what would change the answer. Use this whenever the user asks to evaluate or compare technologies, vendors, or architectures ("Kafka or Kinesis?", "which vector DB for our RAG stack?"); analyze, review, or reverse-engineer an existing system or codebase's architecture; research the state of the art in a technical domain; write a design doc, tech brief, architecture review, or ADR-scale analysis; or asks for "insights", "perspective", "a deep dive", "a report", or diagrams on a technical topic — even when they never say the word "report". Also use for reviewing AI/agent/LLM system architec

nguyenvanphituoc Updated 3 repo stars
Terminal recording: a worker tries to edit a file outside the scope it was given, a PreToolUse hook denies the write and names the path, and the next edit insid

File contents

nguyenvanphituoc/shapeup-sdlc-plugin commit ac98390e9b

Frequently asked questions

npx get-skill add nguyenvanphituoc/architecture-research-report