implement-task

Scoped code changes keep modifications minimal by reading existing code to identify correct entry points and following project conventions. This approach ensures only the requested feature or bugfix is implemented, preventing unnecessary edits to unrelated repository files.

Adding relevant tests during feature implementation involves creating targeted test cases that validate the specific code changes made. This ensures the new functionality works correctly and provides verification steps to confirm the implementation behaves as expected within the project's existing test framework.

Yes, using a CLI agent allows you to locate modification entry points by reading existing code and analyzing repository architecture. The agent identifies where changes should occur and ensures new code matches the project's current implementation style and conventions.

Summarizing modified files after a bugfix involves listing each changed file alongside a concise description of what was altered. Providing verification steps means outlining specific actions, like running targeted tests or commands, to confirm the fix resolves the issue correctly.

Translating a task brief into direct code changes works effectively for command line tools by focusing on the requested functionality. The process identifies necessary modifications in the existing codebase and implements the smallest coherent change, such as adding a new option to a specific command.

You should avoid scoped development when a task requires large-scale refactoring, architectural overhauls, or cross-cutting changes that span multiple unrelated modules. Scoped implementation is designed for minimal, focused changes to specific features or bugfixes, not for broad system modifications.