review-feedback

You are reviewing a document that contains feedback comments tagged with one or more configured prefixes (e.g., [MK], [REV]). Tags and their interpretation rules are configured per-user in ~/.mstack/dev/feedback-tags.json.

Step 0: Load feedback tag configuration

Run this bash to check for the config file:

mkdir -p ~/.mstack/dev
CONFIG=~/.mstack/dev/feedback-tags.json
if [ -f "$CONFIG" ] && [ -s "$CONFIG" ]; then
  cat "$CONFIG"
else
  echo "MISSING"
fi

If output is MISSING (first run)

1. Create the file with the default MK entry. Use the Write tool to write ~/.mstack/dev/feedback-tags.json with this content:

   {
     "tags": [
       {
         "tag": "MK",
         "from": "Document author (initials = MK for Mayank)",
         "content": "Direct edit instructions, factual corrections, rephrasing requests, structural changes",
         "action": "Apply edits as written; treat as imperative; only push back if ambiguous"
       }
     ]
   }
   

2. Tell the user verbatim:

   Saved your feedback tag config to ~/.mstack/dev/feedback-tags.json. Pre-seeded with MK as the default. Edit this file directly to add, modify, or delete tags later.

3. Use AskUserQuestion: "Want to add another tag now? You can also add more later by editing the file." with options:

   • A) No, continue with MK
   • B) Yes, add another tag

4. If the user picks B, ask 4 questions in sequence (one AskUserQuestion call each, free-text answers):

   • "What tag prefix? (short uppercase letters only — e.g., REV, FB, TODO. Will be matched case-insensitively in documents.)"
   • "Who are these comments from? (e.g., 'External reviewer')"
   • "What do these comments typically contain? (e.g., 'Suggestions and open questions')"
   • "What action should I take with these comments? (e.g., 'Treat as suggestions; flag for discussion before applying')"

   Read the current config, append the new tag object to the tags array, write the updated file. Then ask "Add another?" again — loop until user says no.