human-architect-mindset

Document domain concepts, dependency maps, and trade-offs for architecture decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/scamai/scamai-landing --skill human-architect-mindset-scamai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-architect-mindset
Source: https://github.com/scamai/scamai-landing/tree/main/.agents/skills/human-architect-mindset
Command: npx skills add https://github.com/scamai/scamai-landing --skill human-architect-mindset-scamai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI can generate code, but humans must decide what to build, why it matters, and whether it can ship. Organizations often struggle with domain understanding, cross-team dependencies, and conflicting constraints when designing multi-component systems. This skill provides a structured approach centered on loyalty to architectural commitments, across domain modeling, systems thinking, constraint navigation, AI-aware decomposition, and AI-first development, to guide strategic decisions and ensure outcomes are ship-ready.

Core Features & Use Cases

  • Domain modeling for accurate problem framing
  • Systems thinking to map dependencies and failure modes
  • Constraint navigation to surface blockers early
  • AI-aware decomposition for bounded, verifiable tasks
  • AI-first evaluation to select practical patterns and tools

Quick Start

Announce at the start that you are using the Human Architect Mindset to guide the architectural thinking.

Frequently Asked Questions about human-architect-mindset

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

FAQPage Schema
How do I map cross-team dependencies and constraints for multi-component architecture?

Map cross-team dependencies and constraints for multi-component architecture by applying systems thinking and constraint navigation. This surfaces blockers, integrates conflicting constraints, and produces shipable designs with verifiable domain concepts and explicit trade-offs.

What is AI-aware decomposition for bounded, verifiable tasks?

AI-aware decomposition for bounded, verifiable tasks is an architectural method that breaks complex systems into smaller components. It requires documenting domain concepts and dependency maps to ensure AI-generated outcomes remain auditable and ship-ready.

How do I navigate conflicting technical and non-technical constraints in system design?

Navigate conflicting technical and non-technical constraints in system design by documenting explicit trade-offs and applying constraint navigation. This integrates politics and regulatory considerations to preserve loyalty to architectural commitments.

When do I need domain modeling for accurate problem framing in AI-first development?

You need domain modeling for accurate problem framing in AI-first development when organizations struggle with domain understanding. It provides a structured approach to decide what to build and why it matters before AI generates code.

Does this approach work for multi-team projects with regulatory considerations?

Yes, this approach works for multi-team projects with regulatory considerations. It applies systems thinking and constraint navigation across technical and non-technical constraints to produce shipable, auditable outcomes that preserve loyalty to commitments.

What is the best way to document architectural trade-offs for auditable outcomes?

The best way to document architectural trade-offs for auditable outcomes is to explicitly record domain concepts, dependency maps, and bounded AI tasks. This structured approach ensures verifiable designs that preserve loyalty to architectural commitments.