Architecture Approach Selection

Given a feature/project's context (scale, team, timeline, domain, constraints — via batched AskUserQuestion rounds), surfaces candidate architectural approaches, defaulting to the simplest option that works, grounded in internal decision trees plus current web-researched practice for the specific domain (offline-first sync, search, background jobs, multi-tenancy, real-time collaboration, and others as they come up) — then writes its own deep-dive-style selection document. Use when asked "what methods/approaches can I use for this", "what's the right architecture/stack for this", or before committing to a pattern (monolith vs. microservices, sync vs. event-driven, Repository vs. direct ORM, REST vs. GraphQL, how much DDD). NOT for the PRD (`breakdown-feature-prd`), validating a vague idea (`brainstorming`), a full implementation plan (`breakdown-feature-implementation`), or the ADR (`documentation-and-adrs`) — this picks the approach; those build it out or record it later.

Ghosteken Updated
DEFINE → PLAN → BUILD → VERIFY → REVIEW → SHIP pipeline

File contents

ghosteken/agent-harness commit 36055bdea3

Frequently asked questions

npx get-skill add ghosteken/architecture-approach-selection