=minor prompt improvements

Author: dil-asomlai

prompt-library/3-implmentation-plan-generation.md

@@ -16,7 +16,9 @@ Input
 ⸻
 
 Instructions
-
+0. Check MCP Access
+   - Confirm whether an active Atlassian MCP connections is available.
+   - If no MCP connection is detected, terminate the task immediately and return: "No MCP connection. Execution stopped."
 1. Understand the Request
    - Identify the main feature or bug fix
    - Extract key technical details: inputs, outputs, edge cases, dependencies, constraints
@@ -31,7 +33,6 @@ Instructions
    - Ensure the prompt is self-contained and ready to use by an AI agent
    - Use @planning-guide.md
 4. Post the Prompt to the Ticket
-   - Ask if the user wants to do this step. Execute only if stated so.
    - Post the generated prompt as a comment on the related issue or ticket. Consider using MCP. It must be added to the ticket or issue
    - Prefix the comment with a line including: `**[AI generated] [Implementation prompt]**` to indicate the source.
 

prompt-library/4-feedback-request-review.md

@@ -1,8 +1,6 @@
 0. **Verify MCP Access**
-
-- Confirm that the GitHub MCP connection is active
-- If no connection is available, terminate immediately and return: "No MCP connection. Cannot open pull request."
-
+   - Confirm that the GitHub MCP connection is active
+   - If no connection is available, terminate immediately and return: "No MCP connection. Cannot open pull request."
 1. **Verify the Changes:**
    - Use the known verification methods (e.g., tests, manual steps, QA guidelines) to confirm that the changes are correct and working as intended
    - Fix the issues if you identify any