architect

Creates architecture decision records, component diagrams, and risk assessments.

105|12|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill architect-tmcfarlane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/architect
Command: npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill architect-tmcfarlane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers often struggle to translate high-level goals into scalable, maintainable system architectures. This Skill provides structured guidance to craft architecture visions, evaluate trade-offs, and document decisions.

Core Features & Use Cases

  • Define system boundaries, components, and interfaces for new initiatives.
  • Produce Architecture Decision Records (ADRs) and architecture diagrams.
  • Assess non-functional requirements, risks, and migration paths for refactors.

Quick Start

Outline a high-level architecture and ADR plan for a proposed subsystem to establish design direction.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create an Architecture Decision Record for a new software subsystem?

To create an Architecture Decision Record, outline your proposed subsystem to evaluate components, constraints, and trade-offs. This process establishes design direction by satisfying the creation of ADRs, component diagrams, and interface definitions.

What is the best way to evaluate trade-offs for a major system refactor?

Evaluating trade-offs for a major system refactor requires assessing non-functional requirements, risks, and migration paths. This approach translates high-level goals into maintainable system architectures by documenting technical strategy decisions.

How do I define system boundaries and interfaces for high-level technical strategy?

Defining system boundaries and interfaces involves structuring your high-level technical strategy to evaluate components across teams. This provides clear architecture visions and produces component diagrams for new initiatives.

Can I use this approach for both new system design and major refactors?

Yes, this approach applies to initiatives requiring evaluation of components and trade-offs across teams, from new subsystem design to major refactors. It helps architects translate high-level goals into scalable, maintainable system architectures.

When do I need a formal risk assessment and testing plan for software architecture?

You need a formal risk assessment and testing plan when translating high-level goals into scalable system architecture. This ensures non-functional requirements and migration paths are properly evaluated for new initiatives or refactors.