Update README.md

Author: jfy133

README.md

@@ -23,23 +23,24 @@ To make a new proposal for a special interest group, please create a new issue i
 
 The curator workflow is as follows:
 
-1. Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
-2. Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding).
-3. Acceptance requires a minimum of OKs from:
+- [ ]  Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
+- [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding).
+- [ ] Acceptance requires a minimum of OKs from:
     - Two members of the core team.
     - One member of the core team and one member of the maintainers team.
-5. If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
-6. If a proposal is turned down, update both the label AND  status to 'turned-down', and when closing select 'Close as not planned'
-7. If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
+- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
+- [ ] If a proposal is turned down, update both the label AND  status to 'turned-down', and when closing select 'Close as not planned'
+- [ ] If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
+- [ ] Complete the reemaining new-pipeline onboarding tasks listed [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding)
 
 ### Special Interest Groups
 
 The curator workflow is as follows:
 
-1. Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
-2. Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/blog/2024/special_interest_groups).
-3. Acceptance requires a minimum of OKs from:
+- [ ] Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
+- [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/blog/2024/special_interest_groups).
+- [ ] Acceptance requires a minimum of OKs from:
     - Two members of the core team.
-5. If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
-6. If a proposal is turned down, update both the label AND  status to 'turned-down', and when closing select 'Close as not planned'
-7. If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
+- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
+- [ ] If a proposal is turned down, update both the label AND  status to 'turned-down', and when closing select 'Close as not planned'
+- [ ] If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'