diff --git a/README.md b/README.md
index cefffc9..d08c2b9 100644
--- a/README.md
+++ b/README.md
@@ -43,17 +43,13 @@ The default is to deploy to staging:
 
 ## Rake
 
-Kumade auto-generates a deploy:ENV task for every Heroku environment.
-
-    # in your Rakefile:
-    require 'kumade/railtie'
-    # Kumade must be required before this line
-    Blog::Application.load_tasks!
+Kumade auto-generates a deploy:ENV task for every Heroku environment. You don't
+need to do anything to get the Rake tasks, they're automatically set up for you.
+They're of the form deploy:ENV, so if you have a "staging" remote, you would
+run:
 
     $ rake deploy:staging
 
-If you use rake tasks, you can't pass in options (like -p/--pretend).
-
 ## Does it support the Cedar stack?
 
 Yes. Kumade will automatically detect if your app is running on Cedar.
diff --git a/features/railtie.feature b/features/railtie.feature
index 974e472..a548d0e 100644
--- a/features/railtie.feature
+++ b/features/railtie.feature
@@ -6,8 +6,7 @@ Feature: Railtie
   @creates-remote @disable-bundler @slow
   Scenario: Rake tasks are loaded
     Given a new Rails application with Kumade
-    When I require the kumade railtie in the Rakefile
-    And I create a Heroku remote named "staging"
+    When I create a Heroku remote named "staging"
     And I create a non-Heroku remote named "bad_remote"
     Then the rake tasks should include "deploy:staging" with a description of "Deploy to staging environment"
     But the rake tasks should not include "deploy:bad_remote"
diff --git a/lib/kumade.rb b/lib/kumade.rb
index f16d8ba..13c3b18 100644
--- a/lib/kumade.rb
+++ b/lib/kumade.rb
@@ -1,8 +1,9 @@
+require 'kumade/railtie'
+
 module Kumade
   autoload :Git,             "kumade/git"
   autoload :Deployer,        "kumade/deployer"
   autoload :CLI,             "kumade/cli"
-  autoload :Railtie,         "kumade/railtie"
   autoload :DeploymentError, "kumade/deployment_error"
   autoload :Configuration,   "kumade/configuration"
   autoload :Heroku,          "kumade/heroku"