diff --git a/proposals/proposal-Continue-Exit-For-With-Loop-Identifier.md b/proposals/proposal-Continue-Exit-For-With-Loop-Identifier.md
new file mode 100644
index 0000000..e75bb89
--- /dev/null
+++ b/proposals/proposal-Continue-Exit-For-With-Loop-Identifier.md
@@ -0,0 +1,247 @@
+# Continue Exit For Identifier
+
+* [x] [Proposed](https://github.com/dotnet/vblang/issues/186)
+* [x] Prototype: [Prototype/ContinueForIdentifier](https://github.com/AdamSpeight2008/roslyn-AdamSpeight2008/tree/Prototpye/ContinueForID)
+* [ ] Implementation: [Not Started](https://github.com/dotnet/roslyn/BRANCH_NAME)
+* [ ] Specification: [Not Started](pr/1)
+
+## Summary
+[summary]: #summary
+
+Extend the capibility of `Contine For` and `Exit For` to enable continuing or exitting a loop nested higher.
+Eg. `Continue For x` and `Exit For x`
+
+-------
+
+## Motivation
+[motivation]: #motivation
+
+* Why are we doing this?
+ * Seems like natural extension to the language, given that the `Next` can also have an identifer. eg `Next x`
+ * It can be difficult to implement workarounds, or require used different loop constructs at different nestings.
+ * Often implemented via `label`s and `GoTo`s. eg `GoTo start_of_loop_x`.
+* What use cases does it support?
+ * This proposal is tightly focused on two cases;
+ * `Continue For loop_identifier`
+ * `Exit For loop_identifier`
+ * It can difficult to implement, resorting to using `label` and `GoTo` eg `GoTo start_of_loop_x`
+* What is the expected outcome?
+ * Without an identifier eg `Continue For` or `Exit For` will perform exactly as it does now.
+ * With an identifier
+ * `Continue For x` will continue with the next iterator of the loop named with the identifier `x`.
+ * `Exit For x` will exit the loop named with the identifier `x`. Resuming execution at the next statement after it.
+
+------
+
+## Detailed design
+[design]: #detailed-design
+
+### Syntax Node Changes
+ An additional optional child node `` will added to
+ * `ExitStatementSyntax`
+ * `ContinueStatementSyntax`
+ This additional node is used to identify which loop identifier to the statement refers to.
+ If the identifier is absent, the statement refers to current loop.
+
+ExitStatementSyntax change
+
+```xml
+
+
+ An exit statement. The kind of block being exited can be found by examining the Kind.
+
+
+ 10.11
+ ExitStatement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The "Exit" keyword.
+
+
+
+
+ The keyword describing the block to exit.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
ContinueStatementSyntax change
+
+```xml
+
+
+ Represents a "Continue (block)" statement. THe kind of block referenced can be determined by examining the Kind.
+
+
+ 10.11
+ ContinueStatement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The "Continue" keyword.
+
+
+
+
+ The "Do", "For" or "While" keyword that identifies the kind of loop being continued.
+
+
+
+
+
+
+
+
+```
+
Example Code:
+
+```vbnet
+Imports System
+Module M1
+ Sub Main()
+ dim continueLoop as Boolean = true
+ For i = 0 To 2
+ Console.WriteLine($"Loop i Block Start ({i})")
+ For j = 0 To 2
+ Console.WriteLine($"Loop j Block Start ({i})")
+ If continueLoop Then
+ Console.WriteLine("Continuing")
+ continueLoop = false
+ Continue For i
+ End If
+ Console.WriteLine("Exiting")
+ Exit For i
+ Console.WriteLine($"Loop j Block End ({i})")
+ Next j
+ Console.WriteLine("After Loop j")
+ Console.WriteLine($"Loop i Block End ({i})")
+ Next
+ Console.WriteLine("After Loop i")
+ End Sub
+End Module
+```
+
+Expected Output
+
+```
+Loop i Block Start (0)
+Loop j Block Start (0)
+Continuing
+Loop i Block Start (1)
+Loop j Block Start (0)
+Exiting
+After Loop i
+```
+
+