tracking-tasks — Task Persistence & Lifecycle Synchronization

Operating Invariants

• Storage Exclusivity: Mutate task records exclusively in the configured tracker from .agents/task-tracker.md (Local Markdown .agents/tasks/, GitHub Issues, GitLab, or Linear); never touch production code.
• State Integrity: Maintain canonical states: ready, in-progress, done. Treat blocked as a derived state based on prerequisite tasks; a task is only ready when all predecessor dependencies are done.
• Idempotent Synchronization: Check existing issues/files before creating; re-read after writing to verify IDs and persistence.
• Self-Contained Payloads: Embed acceptance criteria, verification commands, and parent traces into the stored task body so subagents can execute independently.
• Adaptive Invocation Output: Render a persistence summary table for humans; emit a compact micro-token for autonomous runners.

Domain Rubric

1. Tracker Resolution

Read .agents/task-tracker.md. If absent, stage local Markdown storage under .agents/tasks/<feature-slug>/ using <NN>-<slug>.md naming conventions (via references/issue-tracker-local.md). Honor remote tracking (gh, glab, Linear) when authenticated CLI access is confirmed. When formatting task bodies, adhere to references/task-template.md.

2. State & Task Lifecycle Transitions

• STAGED: Tasks partitioned and ready for persistence authorization.
• DONE: Tasks verified persisted in tracker storage; implementation remains pending.
• UNRESOLVED: Tracker communication failure or missing authorization.