chore: add pattern exploration jira template

CONTRIBUTING.md

@@ -8,8 +8,6 @@
 
 ## Package Requirements
 
-![Image of good structure](https://cdn.discordapp.com/attachments/293855810063302657/599371250925699072/unknown.png)
-
 - [ ] a `package.json` file with the following sub-requirements:
   - The following scripts: `build, build:dev, clean, type-check, prepublishOnly`.
   - Author must be `Twilio Inc.`
@@ -42,4 +40,4 @@
 
 ## Standard Operating Procedures
 
-All contributions must abide by our [Standard Operating Procedures](https://github.com/twilio-labs/paste/blob/main/STANDARD_OPERATING_PROCEDURES.md). This helps us mitigate errors caused by oversight or forgetfulness by leaning on lessons learned through past mistakes.
+All contributions must abide by our [Standard Operating Procedures](https://github.com/twilio-labs/paste/blob/main/internal-docs/engineering/standard-operating-procedures.md). This helps us mitigate errors caused by oversight or forgetfulness by leaning on lessons learned through past mistakes.

internal-docs/process/epic-template.md

@@ -72,12 +72,19 @@ _Create this as a placeholder. Add details as they come to light, or close the t
 
 _If the component API is somewhat unknown, this ticket can be done before building the component package. If the API is known, this can be closed as “won’t do”._
 
-- Research what other design system libraries are currently doing for their version
-- Build prototypes in CodeSandbox to explore possible API directions
-- Review prototypes with DSYS
+- Research what other design system libraries are currently doing for their version.
+- Build prototypes in CodeSandbox to explore possible API directions.
+- Review prototypes with DSYS.
 - Post the API exploration and spec (coordinate with whoever's writing the spec) on Github as an RFC.
   - Decide what the component API should be. Add a link in the corresponding component package ticket, or create the ticket.
 
+### Create initial pattern layout
+
+_If the design is straightforward and/or has limited interactions, this can be closed as “won’t do”._
+
+- Build prototypes in Storybook to make sure components in the pattern work together so we can check accessibility early. Base these prototypes on the most varied iterations Design currently has (choose < 3) to help check for feasability and uncover any usability issues.
+- Review prototypes with DSYS.
+
 ### Create component package
 
 _If the full component can’t be completed in one sprint, split this ticket up for the different variations of this component._