test the waters before diving in

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 701e56b..74af3fa 100644 (file)
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,13 +1,14 @@
 Contribute
 ==========
 
-So you've got an awesome idea to throw into WP-CLI. Great! Here's the process, in a nutshell:
+Whether you want to fix a bug or implement a new feature, the process is pretty much the same:
 
+0. [Search existing issues](https://github.com/wp-cli/wp-cli/issues); if you can't find anything related to what you want to work on, open a new issue so that you can get some initial feedback.
 1. [Fork](https://github.com/wp-cli/wp-cli/fork) the repository.
 2. Make the code changes in your fork.
 3. Open a pull request.
 
-It doesn't matter if the code isn't perfect. The idea is to get feedback early and iterate.
+It doesn't matter if the code isn't perfect. The idea is to get it reviewed early and iterate on it.
 
 If you're adding a new feature, please add one or more functional tests for it in the `features/` directory. See below.