issue-management

Sequential issue tracking is done by reading an issues directory, checking a .status.json file, and selecting the first pending issue with satisfied dependencies. The agent marks the issue in_progress, completes the work with verification, and updates the status file before moving to the next issue.

Automated issue management uses a structured status file to monitor progress and enforce dependency checks before starting work. The system reads issues from a directory, verifies that dependencies are satisfied, and ensures all acceptance criteria and tests pass before marking an issue completed.

Issue completion criteria are managed by updating .status.json with structured status values like pending, in_progress, and completed. The file tracks the current issue, historical states, and timestamps, ensuring tests pass and documentation is updated before marking an issue as completed.

Yes, this workflow applies to projects with multiple issues and formal dependencies. It prevents misaligned work by checking dependency satisfaction in .status.json before selecting an issue, ensuring no pending issue starts until its prerequisites are completed.

Agents skip dependencies when lacking a structured status file to enforce checks. By requiring .status.json with explicit dependency verification and sequential status updates, the workflow guarantees that no issue starts unless all dependencies are completed and no other issue is in_progress.