architect

Name: architect
Availability: InStock
Author: spumer

Translate feature requirements into bounded contexts and explicit integration contracts.

10|1|Updated Feb 6, 2026

Search Tags:#design #architecture #sdlc #contracts #data-flow #bounded-contexts #architecture-document

Ready to run

npx skills add https://github.com/spumer/i-m-senior-developer --skill architect-spumer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/spumer/i-m-senior-developer/tree/main/plugins/sdlc/skills/architect
Command: npx skills add https://github.com/spumer/i-m-senior-developer --skill architect-spumer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects translate feature requirements into bounded contexts and explicit contracts for system design. This practice clarifies ownership, interfaces, and sequencing, reducing drift between design and implementation.

Core Features & Use Cases

Bounded-context mapping: partition the system into well-defined domains with explicit ownership.
Contract-based hand-offs: define input/output/error shapes for cross-context interactions.
Architecture document generation: produce architecture artifacts that guide downstream implementers.
Open questions surface: surface decisions requiring stakeholder input prior to implementation.

Quick Start

Create an architecture outline from the feature description and generate the architecture document before any implementation starts.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I translate feature requirements into bounded contexts for system design?▼

Bounded contexts partition the system into well-defined domains with explicit ownership, clarifying interfaces and reducing drift between design and implementation. This mapping defines clear boundaries for data flow delineation and cross-context handoffs.

What is contract-based architecture design and when do I need it?▼

Contract-based architecture design defines explicit input, output, and error shapes for cross-context interactions to ensure design fidelity before implementation. You need it when system design requires strict integration contracts and clear ownership delineation across multiple bounded contexts.

How do I generate an architecture document before starting implementation?▼

Generating an architecture document requires translating feature requirements into bounded contexts, explicit contracts, and stack-aware references. This process produces architecture artifacts that guide downstream implementers and surfaces open questions requiring stakeholder decisions prior to coding.

Does this architecture design approach work without writing any code?▼

Yes, this architecture design approach works without writing code by enforcing design discipline and producing architecture documents instead of implementations. It focuses entirely on system design artifacts, data flow delineation, and surfacing open questions for stakeholder input.

What's the best way to surface open questions for stakeholder decisions during system design?▼

The best way to surface open questions during system design is translating feature requirements into bounded contexts and explicit contracts, which identifies missing decisions requiring stakeholder input. This surfaces gaps in integration contracts and cross-context handoffs before implementation starts.

When should I not use bounded context mapping for architecture design?▼

You should avoid bounded context mapping when feature requirements lack sufficient clarity for domain partitioning, or when system design scope does not involve complex cross-context interactions. Without explicit integration contracts and data flow delineation needs, the overhead outweighs the benefits.