diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 6871094f5c..7daff3f1ab 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -8,10 +8,13 @@ the issue. One way we prioritize issues is by the number of :+1: reactions on
 their descriptions. Please DO NOT add `+1` or :+1: comments.
 
 ### Feature requests and proposals
+
 We're excited to hear how we can make Svelte better. Please add as much detail
-as you can on your use case.
+as you can on your use case. To propose an implementation of a large feature or
+change, please create an [RFC](https://github.com/sveltejs/rfcs).
 
 ### Bugs
+
 If you're filing an issue about a bug please include as much information
 as you can including the following.
 
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index e533c21c96..923bfdb50c 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -7,6 +7,11 @@ assignees: ''
 
 ---
 
+<!--
+If you'd like to propose an implementation for a large new feature or change then please create an RFC:
+https://github.com/sveltejs/rfcs
+-->
+
 **Is your feature request related to a problem? Please describe.**
 A clear and concise description of what the problem is. For example: I'm always frustrated when [...]
 
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 7bd900ac33..d14a0f9fe4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,8 +1,7 @@
-
-
 ### Before submitting the PR, please make sure you do the following
-- [ ] It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.
-- [ ] This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
-- [ ] Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to `npm run lint`!)
+- [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
+- [ ] This message body should clearly illustrate what problems it solves.
+- [ ] Ideally, include a test that fails without this PR but passes with it.
+
 ### Tests
--  [ ] Run the tests with `npm test` or `yarn test`)
+-  [ ] Run the tests with `npm test` and lint the project with `npm run lint`
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c3eff81da3..a1e92d3924 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -43,13 +43,16 @@ When [opening a new issue](https://github.com/sveltejs/svelte/issues/new/choose)
 - **One issue, one bug:** Please report a single bug per issue.
 - **Provide reproduction steps:** List all the steps necessary to reproduce the issue. The person reading your bug report should be able to follow these steps to reproduce your issue with minimal effort. If possible, use the [REPL](https://svelte.dev/repl) to create your reproduction.
 
+## RFCs
+
+If you'd like to propose an implementation for a large new feature or change then please [create an RFC](https://github.com/sveltejs/rfcs) to discuss it up front.
+
 ## Installation
 
 1. Ensure you have [npm](https://www.npmjs.com/get-npm) installed.
 1. After cloning the repository, run `npm install` in the root of the repository.
 1. To start a development server, run `npm run dev`.
 
-
 ## Pull requests
 
 ### Your first pull request