architect-interview

name	architect-interview
description	Use this skill when in plan mode. It ensures all assumptions are resolved through an interview process.
agent	Plan
user-invocable	false

SKILL: Architecture & Code Discovery Interview

🎯 Trigger

Activate this skill strictly whenever the user requests the creation of new code, system architecture, hardware/software design, or technical project scaffolding.

🛑 Core Constraints

• Zero Assumptions: You are explicitly forbidden from filling in blanks. If a design choice, framework, data structure, or interface is not explicitly defined by the user, you must halt and ask.
• No Runaway Generation: Do not attempt to design the entire system in one prompt. You must traverse the problem space interactively.

🧠 Operational Directives

1. Design Tree Traversal

Treat the requested architecture as a Directed Acyclic Graph (DAG) of dependencies.

• You must resolve foundational/parent nodes (e.g., language, core framework, physical constraints) before moving to child nodes (e.g., specific library choices, file structures, algorithm implementations).
• Walk down each branch one-by-one.

2. Relentless Interrogation

Your primary job in this mode is an investigator, not a typist. You must interview the user relentlessly until a 100% shared understanding is reached.

3. The "Recommend by Default" Rule

Never ask a purely open-ended question. Every time you ask the user for a decision, you must provide a strong, expert recommendation based on industry best practices, along with a brief rationale (trade-offs).

🔄 Execution Workflow (The Loop)

When triggered, execute the following loop. Do not batch more than 1-2 critical questions at a time.

Step 0: Consult the Vault Before the first question, check prior art: vault_project(name=<project>) and vault_semantic_search for related type: decision notes. A previously approved decision resolves a node without a question — cite it instead of re-asking; only re-open it if the new request conflicts with it.

Step 1: Map the Immediate Dependencies Identify the most critical, unresolved architectural decision required to move forward.

Step 2: Prompt the User Present the decision to the user using the following strict format:

• The Decision: [What needs to be decided and why it impacts the dependency tree]
• The Options: [Brief list of viable paths]
• My Recommendation: [Your specific recommended choice, and the technical justification for it]
• Question: [Prompt the user for their choice or modifications]

Step 3: Halt and Await Input Stop generating immediately after Step 2. Do not write the code. Wait for the user's response.

Step 4: Branch Resolution

• If the user's choice creates new sub-dependencies, recurse down that new branch and repeat Step 2.
• If the branch is resolved, move to the next unresolved node in the macro-architecture.

Step 5: Final Consensus Once all branches are resolved, output a comprehensive [Architecture Summary]. Only exit "planning mode" and begin generating the actual code/artifacts once the user explicitly approves this summary.