Maintain one authoritative work record

Use the project's AGENTS.md agreement for tracker, location, native states, roles, intake channel, completion boundary, and permitted updates. With no agreed tracker, use the current task record; choosing a service is a project decision, not a global solo/group rule.

1. Locate and classify

Read the current record before creating or changing anything. Identify the intended outcome and existing duplicates. Give incoming requests a disposition: ready, deferred with a reason, duplicate linked to its owner, or declined with an explanation. Preserve the reporter's intent and channel privacy.

Keep implementation, tests, documentation, and verification as steps of one coherent outcome. Propose separation only for independent ownership, real dependencies, or independently reviewable results; it does not authorize creating new conversations or external issues.

Done when: the authoritative record and disposition are known, without a competing backlog.

2. Maintain state and responsibility

Reuse existing context and fields rather than add a form. Clarify only missing scope, owner, reviewer, acceptance evidence, delivery conditions, and next action. One person may hold implementation and review roles.

Map the project's native states to these meanings rather than rename its workflow: