What problem does it solve? Choosing between a wiki, a structured database, or a hybrid system for AI-native knowledge management is hard, and picking wrong leads to wiki drift, database gaps, or constant re-derivation of understanding. This Skill interviews you about your usage profile, operational needs, and current pain points, then delivers a direct, opinionated architecture recommendation. ## Core Features & Use Cases - Structured Intake Interview: Asks grouped questions about usage profile, operational needs, and current pain, waiting for answers before proceeding. - Signal-Based Diagnosis: Maps your answers against explicit wiki, database, and hybrid signal criteria rather than defaulting to a safe middle option. - Full Recommendation Document: Produces a diagnosis, recommendation, fit rationale, failure modes of rejected options, risk profile, implementation checklist, and upgrade path. - Use Case: A solo researcher drowning in papers and notes answers the intake questions and receives a concrete wiki-first architecture with a 6-step implementation checklist and criteria for when to add a database layer. ## Quick Start Use the knowledge-architecture-advisor skill to help me decide whether to build a wiki, a database, or a hybrid system for managing my research notes and team knowledge.