entrevistador

Guided user interviews in Obsidian are conducted one question at a time, following up for depth on superficial answers. The session reads and writes directly to interview markdown files, updating frontmatter status and populating response sections.

Conversational data collection is structured by centralizing responses into dedicated markdown files with frontmatter tracking. This removes ambiguity and ensures specialist agents receive fully clarified needs or product data to unblock downstream tasks.

Yes, in-progress interviews can be resumed. The system reads the existing markdown file, checks the frontmatter status, and continues the guided conversational flow exactly where the previous session left off.

Interview status is tracked using frontmatter fields in the markdown files. The system automatically updates status to em-andamento or concluida, and records start and conclusion timestamps to coordinate with project workflows.

Yes, the interview flow is triggered when an agent reports insufficient data. It collects the missing brand or product information through guided questions and reports completion to the project manager to unblock tasks.

This approach requires read and write access to the project's entrevistas index and individual markdown files. It is limited to Obsidian-based project workflows where agents require clarified user data to proceed.