implementlisted

# Implement **Usage:** `/implement [ticket URL, ID, or description]` Use this as the default entry point for a ticket with clear acceptance criteria. Use the lightest process that can prove the requested behavior. Stop and ask for direction when the ticket cannot be read, its acceptance criteria are materially ambiguous, or implementation would require a decision outside the ticket. ## Portable provider policy Use the active environment for implementation. Do not require a particular agent, model, CLI, plugin, or hosted service. If another independent provider is available locally, use it for a read only plan or diff review. Claude, Codex, and OpenCode are examples, not requirements. Keep execution with one provider and use another only to challenge the plan or completed diff. When no independent provider is available, use a fresh reviewer context in the active environment and state that the review was single provider. Never install, configure, authenticate, or invoke a provider solely to satisfy this workflow. Never depend on home directory paths, custom profiles, personal hooks, metrics, queues, databases, background jobs, private credentials, or machine local helper scripts. Repository instructions and available tools are authoritative. ## Setup 1. Read the ticket and its linked requirements. Do not infer scope from an ID alone. 2. Read the repository instructions and the relevant architecture or component docs. 3. Check for an existing branch or worktree for the t