gerente

Obsidian project task management relies on YAML frontmatter, ISO 8601 timestamps, and category checklists to structure work. It decomposes compound requests, maps dependencies, and creates batch tasks after approval to coordinate specialist workflows.

Decomposing complex tasks in an Obsidian vault involves analyzing the request, generating a decomposition plan, and mapping dependencies. Batch tasks are created after approval to ensure coordinated specialist workflows and accurate index synchronization.

Enforcing ISO 8601 timestamps and YAML frontmatter in task checklists requires atomic updates to task and interview indexes. This maintains precise project statistics and prevents duplication across coordinated specialist workflows in the vault.

QA-driven completion updates task timestamps and results, unlocks dependencies, and creates review tasks based on QA findings. This ensures coordinated specialist workflows meet quality standards before index synchronization in the Obsidian vault.

Generating interviews blocks tasks when missing data in Obsidian by linking the interview to the task block. This holds the task until data is provided, synchronizes the interview index, and enables filtered queries by status, agent, or requester.

This task management approach works without executing specialist work by acting as a functional agent that updates documents, task indexes, and interview records. It reports all changes to the Maestro without performing the actual specialized work.