diff --git a/Development.md b/Development.md
new file mode 100644
index 0000000..9605129
--- /dev/null
+++ b/Development.md
@@ -0,0 +1,31 @@
+Working on the modpack requires the [packwiz] tool, so be sure to download it first.
+
+```sh
+packwiz update --all # Update all mods to latest.
+git commit [...]     # Now you can commit your changes..
+git push             # ..and push them to the repository.
+```
+
+It should be noted that packwiz will keep an `index.toml` file and update `pack.toml` to keep track of it, mirroring any changes. However, since these changes are basically build artifacts, we decided to not include them in the repository.
+
+```sh
+# Make sure git will not see any changes to pack.toml.
+# This is to avoid accidentally committing the [index] section.
+git update-index --assume-unchanged pack.toml
+```
+
+To test changes tocally, you can run `packwiz serve` to deploy a simple webserver that just hosts the modpack files. Setting your instance's pre-launch command to the following command will allow it to update from local files when starting up.
+
+```sh
+"$INST_JAVA" -jar packwiz-installer-bootstrap.jar http//localhost:8080/pack.toml
+```
+
+While the game is running, you can use `rsync` to synchronize the `kubejs/` folder after making changes. This allows you to make, for example, recipe changes and test them out in-game, without restarting, simply by running the `/reload` command.
+
+```sh
+# Just replace $PATH_TO_INSTANCE with your instance's location.
+rsync -r --delete kubejs $PATH_TO_INSTANCE/.minecraft
+```
+
+
+[packwiz]: https://github.com/packwiz/packwiz
\ No newline at end of file