diff --git a/_goals/196-Dive_Into_UNIX_and_Bash.md b/_goals/196-Dive_Into_UNIX_and_Bash.md
index 3d52ec9c..5c8044ce 100644
--- a/_goals/196-Dive_Into_UNIX_and_Bash.md
+++ b/_goals/196-Dive_Into_UNIX_and_Bash.md
@@ -61,6 +61,9 @@ Indulge your curiousity and explore the questions that pique your interest.
 ## Specifications
 
 - [ ] Artifact is a GitHub repo.
+
+__FEEDBACK:__ Specs like the two below are super hard to verify. It requires a ton of reading. Its hard to find the 20 exercies or activities. When they've only done 17 of the 20, how do you count that toward completeness? Since this is one checkbox is it pass/fail? Do we have an example of an artifact that meets 100% completeness?
+
 - [ ] 20 exercises are completed from the ["Learn Enough Command Line to be Dangerous"][hartl-command-line] book.
   - [ ] Solution code for each exercise is included in its own bash file (`*.sh`).
   - [ ] Solution code for exercises are stored in a `command-line/` directory of your artifact repo.
@@ -69,6 +72,9 @@ Indulge your curiousity and explore the questions that pique your interest.
   - [ ] Solution code for each activity is included in its own bash file (`*.sh`). **Tip**: for the bash-scripting tutorials, check your solutions by executing your bash (.sh) files (type their name in the terminal), instead of writing code directly in the terminal.
   - [ ] Solution code for activities are stored in a `bash-scripting/` directory of your artifact repo.
   - [ ] Solution code for each activity includes a comment with the prompt text for the activity.
+ 
+__FEEDBACK:__ The spec below should require a certain number of entries in said cheatsheet.
+ 
 - [ ] Cheat sheet of your favorite useful commands and a brief explanation of what they do is included in the artifact as a `cheat-sheet.md` file.
 - [ ] All major features are added via pull requests with a clear description and concise commit messages.
 - [ ] Code uses a linter and there are no linting errors.