diff --git a/docs/Lua API.rst b/docs/Lua API.rst
index 94bca09f1..56e20f9aa 100644
--- a/docs/Lua API.rst	
+++ b/docs/Lua API.rst	
@@ -3756,15 +3756,19 @@ the plugin. See existing files in ``plugins/lua`` for examples.
 blueprint
 =========
 
-Native functions provided by the `blueprint` plugin:
+Lua functions provided by the `blueprint` plugin to programmatically generate
+blueprint files:
 
 * ``dig(start, end, name)``
 * ``build(start, end, name)``
 * ``place(start, end, name)``
 * ``query(start, end, name)``
 
-  ``start`` and ``end`` are tables containing positions (see
-  ``xyz2pos``). ``name`` is used as the basis for the filename.
+  ``start`` and ``end`` are tables containing positions (see ``xyz2pos``).
+  ``name`` is used as the basis for the generated filenames.
+
+The names of the functions are also available as the keys of the
+``valid_phases`` table.
 
 .. _building-hacks:
 
diff --git a/docs/Plugins.rst b/docs/Plugins.rst
index 24dd90c43..a60d343ba 100644
--- a/docs/Plugins.rst
+++ b/docs/Plugins.rst
@@ -37,22 +37,70 @@ For more information, see `the full Stonesense README <stonesense>`.
 
 blueprint
 =========
-Exports a portion of your fortress into QuickFort style blueprint files.
+The ``blueprint`` command exports the structure of a portion of your fortress in
+a blueprint file that you (or anyone else) can later play back with `quickfort`.
 
-Usage::
+Blueprints are ``.csv`` or ``.xlsx`` files created in the ``blueprints``
+subdirectory of your DF folder. The map area to turn into a blueprint is either
+selected interactively with the ``blueprint gui`` command or, if the GUI is not
+used, starts at the active cursor location and extends right and down for the
+requested width and height.
+
+Usage:
+
+    blueprint <width> <height> [<depth>] [<name> [<phases>]] [<options>]
+    blueprint gui [<name> [<phases>]] [<options>]
+
+Examples:
+
+blueprint gui
+    Runs `gui/blueprint`, the interactive blueprint frontend, where all
+    configuration for a ``blueprint`` command can be set visually and
+    interactively.
 
-    blueprint <x> <y> <z> <name> [dig] [build] [place] [query]
+blueprint gui bedrooms dig -\-cursor 108,100,150
+    Starts ``gui/blueprint`` with some configuration options preset to custom
+    values.
 
-Options (If only region and name are given, export all):
+blueprint 30 40 bedrooms
+    Generates blueprints for an area 30 tiles wide by 40 tiles tall, starting
+    from the active cursor on the current z-level. Output is written to the
+    ``bedrooms.csv`` file in the ``blueprints`` directory.
 
-:x,y,z:     Size of map area to export
-:name:      Name of export files
-:dig:       Export dig commands to "<name>-dig.csv"
-:build:     Export build commands to "<name>-build.csv"
-:place:     Export stockpile commands to "<name>-place.csv"
-:query:     Export query commands to "<name>-query.csv"
+Positional Parameters:
+
+:width:   Width of the area (in tiles) to translate.
+:height:  Height of the area (in tiles) to translate.
+:depth:   Number of z-levels to translate. Positive numbers go *up* from the
+          cursor and negative numbers go *down*. Defaults to 1 if not specified,
+          indicating that the blueprint should only include the current z-level.
+:name:    Base name for blueprint files created in the ``blueprints`` directory.
+          If no name is specified, "blueprint" is used by default. The string
+          must contain some characters other than numbers so the name won't be
+          confused with the optional ``depth`` parameter.
+
+Phases:
+
+If you want to generate blueprints only for specific phases, add their names to
+the commandline, anywhere after the blueprint base name. You can list multiple
+phases; just separate them with a space.
+
+:dig:    Generate quickfort ``#dig`` blueprints.
+:build:  Generate quickfort ``#build`` blueprints for constructions and
+         buildings.
+:place:  Generate quickfort ``#place`` blueprints for placing stockpiles.
+:query:  Generate quickfort ``#query`` blueprints for configuring rooms.
+
+If no phases are specified, all blueprints are created.
+
+Options:
 
-Goes very well with `quickfort`, for re-importing.
+:-c, -\-cursor <x>,<y>,<z>:
+    Use the specified map coordinates instead of the current cursor position for
+    the upper left corner of the blueprint range. If this option is specified,
+    then an active game map cursor is not necessary.
+:-h, -\-help:
+    Show command help text.
 
 .. _remotefortressreader: