issue-start

Obsidian issue documents are analyzed to initiate work with an Agent Team by reading issue files, extracting TODOs and dependencies, and validating assumptions. This enables issue selection and execution across project lifecycles.

An Agent Team validates project assumptions by reviewing the extracted TODOs and dependencies from your Obsidian issue documents. This validation process ensures your implementation plan is concrete and actionable before execution begins.

Yes, you can automatically select the next issue by leaving the issue name blank. The workflow identifies dependencies between issues and selects the first incomplete issue to clearly structure the flow of subsequent tasks.

The best way to manage issue dependencies is using a guided workflow that reads your Obsidian issue documents, identifies dependencies between issues, and produces a concrete implementation plan with tasks for the Agent Team to execute.

Yes, the workflow supports team validation across development, planning, and operations projects. It uses Obsidian notes as the starting point for issues, enabling an Agent Team to validate assumptions and produce implementation plans.