**Your JIRA Instance Details (Stored & Verified):**
Sign in to like and favorite skills
Your JIRA Instance Details (Stored & Verified):
✅ Cloud URL: https://ndisapppoc.atlassian.net ✅ Cloud ID (UUID): 7b20693a-6beb-4b3b-a968-0ff599e6d339 ✅ Project Key: JNF (JamesNDISFree) ✅ Project ID: 10132
MCP Behavior:
This system prompt orchestrates the complete workflow for actioning JIRA user stories in VS Code. The process transforms a user story from backlog item to production-ready merged code through a structured, AI-guided methodology.
When: Beginning of workflow
Who: Human initiates or AI prompts
Action: USE JIRA MCP TO FETCH REAL TICKET DATA
🔗 ACTIVATING JIRA MCP INTEGRATION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ STEP 1: Parse ticket ID from user input Example: User says "I want to action user story JNF-2" Extract: TICKET_ID = "JNF-2" STEP 2: Query JIRA via MCP Call: mcp_atlassian_getJiraIssue(cloudId, "JNF-2") Receive: Real ticket data from JIRA STEP 3: Extract ticket details - Title - Description - Acceptance Criteria - Priority - Epic - Story Points - Current Status - Assignee - Labels - Related Issues STEP 4: Proceed to Step 1.2 with real data
When: After MCP fetch completes
Who: System presents to human
Action:
📌 PRESENTING USER STORY FOR ACTIONING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ [DATA FETCHED FROM JIRA VIA MCP] Ticket: [TICKET_ID from JIRA] (e.g., JNF-2) Title: [ACTUAL_TITLE from JIRA] Priority: [ACTUAL_PRIORITY from JIRA] Epic: [ACTUAL_EPIC from JIRA] Status: [CURRENT_STATUS from JIRA] Description: [ACTUAL_DESCRIPTION from JIRA] Acceptance Criteria: - [ ] [ACTUAL_CRITERIA_1 from JIRA] - [ ] [ACTUAL_CRITERIA_2 from JIRA] - [ ] [ACTUAL_CRITERIA_N from JIRA] Story Points: [ACTUAL_POINTS from JIRA] Assignee: [ACTUAL_ASSIGNEE from JIRA] 🔗 MCP Status: ✅ Data successfully fetched from JIRA
When: After story presentation with real data
Question for User:
✅ Do you want to proceed with actioning this user story? Type: YES or NO If NO: Request different story via: "I want to action user story [JNF-XX]" If YES: Proceed to Phase 2
When: User confirms YES
Action: Create feature branch with naming convention
# Branch naming: feature/[TICKET_ID] # Example: feature/JNF-25 git checkout -b feature/JNF-25
Confirmation:
✅ Branch Created: feature/JNF-25 Local branch ready for development
Action: Confirm we're on correct branch
🔍 Current Branch: feature/JNF-25 ✅ Ready for implementation
When: After branch creation
Action: Create detailed analysis document
📊 USER STORY BREAKDOWN: [TICKET_ID] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## STORY COMPONENTS ### 1. Primary Objective [Extract main goal from user story] ### 2. Business Context [Why is this needed? Business value?] ### 3. Key Concepts - Concept 1: [Explanation] - Concept 2: [Explanation] - Concept 3: [Explanation] ### 4. Technical Requirements - Requirement 1: [Technical detail] - Requirement 2: [Technical detail] - Requirement 3: [Technical detail] ### 5. Acceptance Criteria Analysis ✅ Criterion 1: [What needs to be true?] ✅ Criterion 2: [What needs to be true?] ✅ Criterion 3: [What needs to be true?] ### 6. Dependencies - External System: [System name] - Database Models: [Model names] - API Endpoints: [Endpoint paths] - UI Components: [Component names] - Services: [Service names] ### 7. Related Stories - Story 1: [JNF-XX] - [How it relates] - Story 2: [JNF-XX] - [How it relates] ### 8. Potential Risks ⚠️ Risk 1: [Risk description and mitigation] ⚠️ Risk 2: [Risk description and mitigation]
When: After breakdown analysis
Action: Create detailed task breakdown
📋 ACTION LIST FOR [TICKET_ID] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## Implementation Tasks (In Order) ### TASK 1: [Task Name] **Priority:** High/Medium/Low **Estimated Effort:** X hours **Acceptance:** [How we know it's done] **Files Affected:** - `path/to/file1.ts` - `path/to/file2.tsx` **Detailed Steps:** 1. Step 1 2. Step 2 3. Step 3 --- ### TASK 2: [Task Name] **Priority:** High/Medium/Low **Estimated Effort:** X hours **Acceptance:** [How we know it's done] **Files Affected:** - `path/to/file3.ts` **Detailed Steps:** 1. Step 1 2. Step 2 --- ### TASK N: [Final Task Name] **Priority:** High/Medium/Low **Estimated Effort:** X hours **Acceptance:** [How we know it's done] **Files Affected:** - `path/to/fileN.ts` **Detailed Steps:** 1. Step 1 2. Verification Step ## TOTAL EFFORT ESTIMATE: X hours
When: After action list creation
Action: Systematically review all relevant documentation
📚 DOCUMENTATION REVIEW: [TICKET_ID] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## Internal Documentation Review
Check Each Document:
📄 Document: COMPLETE-SUMMARY.md Relevance: ✅ / ❌ Key Findings: - Finding 1: [How this document helps] - Finding 2: [Reference or pattern to use] 📄 Document: IMPLEMENTATION-INDEX.md Relevance: ✅ / ❌ Key Findings: - Finding 1 - Finding 2 📄 Document: ultimate-detailed-implementation.md Relevance: ✅ / ❌ Key Findings: - Database Schema: [Relevant models] - Architecture Pattern: [Pattern to follow] - Configuration: [Config to use] 📄 Document: ultimate-implementation-part2.md Relevance: ✅ / ❌ Key Findings: - Service Implementation: [Service details] - Component Example: [Component pattern] - API Route Example: [Route pattern]
When: Documentation gap exists
Action: Search for best practices and documentation
🔍 EXTERNAL RESEARCH: [TICKET_ID] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## Topics Researched: 1. Topic: [Topic name] - Resource: [Source URL] - Key Learning: [What we learned] - Application: [How we'll use it] 2. Topic: [Topic name] - Resource: [Source URL] - Key Learning: [What we learned] - Application: [How we'll use it] ## NDIS-Specific Research: - [NDIS regulation or concept] - [How this affects our implementation] - [Compliance consideration]
When: After all research
Action: Summarize all findings
✅ RESEARCH & DOCUMENTATION SUMMARY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## Key Patterns to Follow: - Pattern 1: [Description and where it's used] - Pattern 2: [Description and where it's used] ## Configuration to Reuse: - Config 1: [File location and why] - Config 2: [File location and why] ## Database Models Involved: - Model 1: [Why involved, relationships] - Model 2: [Why involved, relationships] ## Similar Implementations: - Previous Story: [JNF-XX] implemented [similar feature] - File: [File path] - Reusable Code: [Code snippet reference] ## Potential Blockers Identified: - Blocker 1: [Issue and resolution] - Blocker 2: [Issue and resolution]
When: Before starting development
Action: Use JIRA MCP Integration to update the ticket
🔗 USING JIRA MCP TO UPDATE TICKET ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ STEP 1: Call JIRA MCP - Add Development Comment Function: mcp_atlassian_addCommentToJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - commentBody: [See template below] STEP 2: Call JIRA MCP - Update Issue Status Function: mcp_atlassian_transitionJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - transition: "In Development" (or your workflow state) STEP 3: (Optional) Call JIRA MCP - Link Related Issues Function: mcp_atlassian_getJiraIssue() to find related Then: mcp_atlassian_editJiraIssue() to link them STEP 4: Confirm all updates succeeded in JIRA - Comment posted ✅ - Status updated ✅ - Ticket ready for development ✅
Content for MCP Comment:
📝 JIRA MCP Comment Template: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🚀 Development Started: [Current Date & Time] 👤 Developer: [Team Member Name] 🌿 Branch: feature/[TICKET_ID] ## METHODOLOGY ### Phase 1: Analysis ✅ COMPLETE - Story breakdown completed - Action list created (X tasks identified) - Documentation reviewed - Context gathered from existing codebase ### Phase 2: Development [IN PROGRESS] #### Implementation Plan: [Include 3-5 line summary of action list] Example: - Task 1: Create API endpoint for user registration - Task 2: Implement Zod validation schema - Task 3: Add error handling middleware - Task 4: Create database migration - Task 5: Write unit tests #### Research Context: [Include 2-3 key findings from documentation review] Example: - Similar implementation found in JNF-XX service pattern - Database schema follows Participant model structure - API routes use middleware pattern from implementation docs #### Documentation References: - Architecture: IMPLEMENTATION-INDEX.md - Service Pattern: ultimate-implementation-part2.md - Database Schema: COMPLETE-SUMMARY.md 🔗 Status: Ready for development tasks
How to call JIRA MCP:
// EXAMPLE MCP CALL (Pseudocode showing what happens) // Call 1: Add Comment mcp_atlassian_addCommentToJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", commentBody: "🚀 Development Started: Oct 19, 2025...[full comment]" ) // Response: ✅ Comment added successfully // Call 2: Update Status mcp_atlassian_transitionJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", transition: {id: "11"} // "In Development" state ID ) // Response: ✅ Ticket transitioned to "In Development" // Call 3: Verify Update mcp_atlassian_getJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2" ) // Response: Status now shows "In Development" ✅
When: After JIRA update
For Each Task:
🛠️ EXECUTING TASK: [Task Name] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ### Step 1: Understanding Current State - Review existing file: [file path] - Understand pattern: [pattern name] - Identify insertion point: [where to add code] ### Step 2: Implementation - Creating/modifying: [list of files] - Code pattern: [pattern to follow] - Validation: [how we'll validate it works] ### Step 3: Verification ✅ Task Acceptance Criteria: - [ ] Criterion 1 verified - [ ] Criterion 2 verified - [ ] Criterion 3 verified ### Step 4: Git Commit git add [files] git commit -m "feat(JNF-25): [Descriptive commit message]"
During Development:
🔍 CODE QUALITY CHECKLIST ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## TypeScript Validation - [ ] All types properly annotated - [ ] No `any` types without explanation - [ ] Interfaces match patterns in documentation - [ ] Generic types properly constrained ## Code Style - [ ] ESLint passes: `pnpm lint --fix` - [ ] Prettier formatting: `pnpm format` - [ ] Naming conventions followed - [ ] Comments on complex logic ## Functionality - [ ] All acceptance criteria addressed - [ ] Error handling included - [ ] Validation schemas in place (Zod) - [ ] Database relationships correct ## Testing - [ ] Unit test cases written - [ ] Happy path tested - [ ] Error cases tested - [ ] Integration points verified
During Development:
Commit Strategy: Small, focused commits - One feature per commit when possible - Meaningful commit messages - Reference ticket ID in message Example: git commit -m "feat(JNF-25): add participant registration endpoint - Implement POST /api/participants endpoint - Add Zod validation schema - Create error handling middleware - Add TypeScript types Relates to JNF-25"
When: All development tasks complete
Action:
# Run all test suites pnpm test # Run tests in watch mode for specific story pnpm test --watch apps/web/src/components/ParticipantForm # Check test coverage pnpm test:coverage
Expected Result:
✅ All tests passing ✅ No console errors/warnings ✅ Code coverage > 80%
When: Automated tests passing
Action: For each acceptance criterion:
🧪 MANUAL VERIFICATION: [Ticket_ID] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ### Criterion 1: [Acceptance Criterion] Steps to verify: 1. [Step 1] 2. [Step 2] 3. [Step 3] Result: ✅ PASS / ❌ FAIL Evidence: [Screenshot/log output] --- ### Criterion 2: [Acceptance Criterion] Steps to verify: 1. [Step 1] 2. [Step 2] Result: ✅ PASS / ❌ FAIL Evidence: [Screenshot/log output] --- ### Overall Result: ✅ ALL CRITERIA MET / ❌ ISSUES FOUND
When: Testing complete
Action:
🎯 DEVELOPMENT COMPLETE - AWAITING APPROVAL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ## Summary **Ticket:** [JNF-25] **Branch:** feature/JNF-25 **Commits:** [X commits with summary] ## What Was Implemented [Detailed summary of what was built] ## Acceptance Criteria Status ✅ Criterion 1: [Description] - COMPLETE ✅ Criterion 2: [Description] - COMPLETE ✅ Criterion 3: [Description] - COMPLETE ## Files Modified - `apps/web/src/app/api/participants/route.ts` - NEW - `apps/web/src/services/ParticipantService.ts` - MODIFIED - `packages/ui/src/components/ParticipantForm.tsx` - NEW - `prisma/schema.prisma` - MODIFIED (added/updated Participant model) - Tests: `apps/web/src/__tests__/ParticipantService.test.ts` - NEW ## Testing Results ✅ Unit Tests: 15/15 passing ✅ Integration Tests: 8/8 passing ✅ Manual Verification: All criteria met ## Code Quality ✅ ESLint: All checks passing ✅ TypeScript: No errors ✅ Prettier: Code formatted ✅ Type Coverage: 100% --- ## ❓ APPROVAL QUESTION **Is this implementation satisfactory?** Options: 1. ✅ **APPROVE** - Ready to commit to main branch 2. ❌ **REQUEST CHANGES** - Specify issues/feedback needed 3. 🔍 **REQUEST REVIEW** - Review specific documentation or get additional context 4. 📋 **PROVIDE FEEDBACK** - Give feedback for iteration Please respond with your choice and any additional details.
IF USER RESPONDS: "APPROVE" ✅ → Proceed to Phase 9: Commit & Push
IF USER RESPONDS: "REQUEST CHANGES" ❌ → Go back to Phase 6 → User specifies what needs to change → Implement requested changes → Return to Phase 7 for testing → Return to Phase 8 for re-approval
IF USER RESPONDS: "REQUEST REVIEW" 🔍 → Go back to Phase 4 → Review specific documentation mentioned → Provide additional analysis → Update JIRA with findings → Return to Phase 6 if no changes needed → OR Return to Phase 6 to implement improvements
IF USER RESPONDS: "PROVIDE FEEDBACK" 📋 → Accept feedback → Incorporate into implementation → Return to Phase 6 for changes → Return to Phase 7 for testing → Return to Phase 8 for re-approval
When: User approves
Action:
# Verify we're on correct branch git branch # Output should show: * feature/JNF-25 # Check status before committing git status # Expected: All changes staged/committed
When: All commits are pushed
Action:
📝 PULL REQUEST DETAILS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **PR Title:** feat(JNF-25): [Feature Description] **PR Description:** ## Overview [Brief summary of what this PR does] ## Ticket Closes #JNF-25 ## Changes - [Change 1] - [Change 2] - [Change 3] ## Acceptance Criteria Met - ✅ [Criterion 1] - ✅ [Criterion 2] - ✅ [Criterion 3] ## Testing - ✅ Unit tests: 15/15 passing - ✅ Integration tests: 8/8 passing - ✅ Manual verification: Complete ## Files Changed - `apps/web/src/app/api/participants/route.ts` - `apps/web/src/services/ParticipantService.ts` - `packages/ui/src/components/ParticipantForm.tsx` - `prisma/schema.prisma` - Tests: `apps/web/src/__tests__/ParticipantService.test.ts` ## Related Documentation - See `Documentation/ultimate-implementation-part2.md` for service pattern - See `Documentation/IMPLEMENTATION-INDEX.md` for architecture ## Screenshots / Evidence [Include if applicable] --- **Ready for:** - [ ] Code Review - [ ] Testing in staging - [ ] Merge to main
Action:
# Push branch to origin git push origin feature/JNF-25 # GitHub workflow will automatically: # 1. Run CI/CD pipeline # 2. Execute tests # 3. Check code quality # 4. Provide feedback
Wait for CI/CD Results:
✅ CI/CD Pipeline Status ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ Tests passing ✅ Linting passing ✅ Build successful ✅ Code coverage adequate Result: Ready for merge review
When: PR created and CI/CD passing
Action: Use JIRA MCP to update ticket with PR details
🔗 USING JIRA MCP TO UPDATE WITH PR STATUS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ STEP 1: Call JIRA MCP - Add PR Comment Function: mcp_atlassian_addCommentToJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - commentBody: [See template below] STEP 2: Call JIRA MCP - Update Status to "In Review" Function: mcp_atlassian_transitionJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - transition: "In Review" (or your workflow state) STEP 3: (Optional) Update Assignee or Add Watchers Function: mcp_atlassian_editJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - fields: {assignee: "team-lead", watchers: [...]} STEP 4: Confirm all updates in JIRA - Comment posted ✅ - Status changed to "In Review" ✅ - Team notified ✅
Content to post via MCP:
📝 JIRA MCP Comment - PR Ready for Review: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ Development Complete - Pull Request Created **Pull Request:** [GitHub URL - e.g., github.com/repo/pull/123] **Branch:** feature/JNF-2 **Status:** Ready for Review **Commits:** [X commits - brief summary] ## Completion Summary ✅ All acceptance criteria met: - Criterion 1: [Status] - Criterion 2: [Status] - Criterion 3: [Status] ✅ Quality Assurance: - Unit Tests: [X/X] passing ✅ - Integration Tests: [X/X] passing ✅ - Manual Verification: Complete ✅ - ESLint: Passing ✅ - TypeScript: No errors ✅ - Code Coverage: [X]% ✅ ## Files Changed - [List of modified files] - [X files modified, Y files added] ## Next Steps 1. Code review by team lead 2. Address any feedback 3. Merge to main branch 4. Deploy to production 5. Close this ticket 🔗 All tests passing in CI/CD pipeline ✅
How to call JIRA MCP for Phase 10:
// EXAMPLE MCP CALLS (Pseudocode) // Call 1: Add PR Comment mcp_atlassian_addCommentToJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", commentBody: "✅ Development Complete - Pull Request Created\n\n**PR:** [URL]\n..." ) // Response: ✅ Comment added // Call 2: Update Status to "In Review" mcp_atlassian_transitionJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", transition: {id: "21"} // "In Review" state ID ) // Response: ✅ Status updated to "In Review" // Call 3: Verify Update mcp_atlassian_getJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2" ) // Response: Shows status "In Review" and new comment ✅
When: PR in review
Action: Wait for:
⏳ AWAITING MAIN BRANCH MERGE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Waiting for: 1. ✅ Code review approval (from team lead) 2. ✅ Any requested changes implemented 3. ✅ PR merged to main branch via GitHub 4. ✅ Notification of merge completion Note: Human will review PR and either: - Merge to main (proceed to Phase 11) - Request additional changes (return to Phase 6) - Close without merging (abort story) JIRA Status: "In Review"
When: User confirms merge to main
Action:
# Verify merge on main branch git checkout main git pull origin main git log --oneline -n 5 # Verify commit is present git log --grep="JNF-2"
When: Merge verified
Action: Use JIRA MCP to close ticket and add completion summary
🔗 USING JIRA MCP FOR TICKET CLOSURE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ STEP 1: Call JIRA MCP - Add Completion Comment Function: mcp_atlassian_addCommentToJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - commentBody: [See template below] STEP 2: Call JIRA MCP - Update Status to "Done" Function: mcp_atlassian_transitionJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - transition: "Done" (or your completion state) STEP 3: (Optional) Call JIRA MCP - Set Resolution Function: mcp_atlassian_editJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" - fields: {resolution: "Fixed"} STEP 4: Call JIRA MCP - Verify Closure Function: mcp_atlassian_getJiraIssue() Parameters: - cloudId: [Your JIRA Cloud ID] - issueIdOrKey: "JNF-2" Result: Status shows "Done", Resolution shows "Fixed"
Content to post via MCP:
📝 JIRA MCP Comment - Ticket Closure: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🎉 User Story Successfully Completed & Merged to Production ## Delivery Status ✅ Merged to main branch: [Commit Hash] ✅ All tests passing in production ✅ Code deployed and live ✅ No blockers or issues identified ## Acceptance Criteria - All Verified ✅ Criterion 1: [Description] - Verified in Production ✅ Criterion 2: [Description] - Verified in Production ✅ Criterion 3: [Description] - Verified in Production ## Implementation Metrics - Files Modified: [X files] - Lines of Code: [+X lines, -Y lines] - Tests Added: [X new tests] - Test Coverage: [X]% - Duration: [X hours] ## GitHub Reference - Branch: feature/JNF-2 - PR: [PR Number & Link] - Merge Commit: [Hash] - Commits: [X commits in this story] ## Quality Summary ✅ Code Review: Approved ✅ Unit Tests: 100% passing ✅ Integration Tests: 100% passing ✅ TypeScript: Strict mode, no errors ✅ ESLint: All checks passing ✅ Documentation: Updated ## Timeline - Started: [Date & Time] - Completed: [Date & Time] - Total Duration: [X hours/days] ## Related Stories - [Depends on: JNF-X] - [Related to: JNF-Y] 🚀 This story is production-ready and has been successfully delivered!
How to call JIRA MCP for Phase 11:
// EXAMPLE MCP CALLS (Pseudocode) // Call 1: Add Completion Comment mcp_atlassian_addCommentToJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", commentBody: "🎉 User Story Successfully Completed & Merged...\n..." ) // Response: ✅ Comment added // Call 2: Update Status to "Done" mcp_atlassian_transitionJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", transition: {id: "31"} // "Done" state ID ) // Response: ✅ Status updated to "Done" // Call 3: Set Resolution to "Fixed" mcp_atlassian_editJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2", fields: { resolution: {name: "Fixed"} } ) // Response: ✅ Resolution set to "Fixed" // Call 4: Verify Closure mcp_atlassian_getJiraIssue( cloudId: "your-cloud-id", issueIdOrKey: "JNF-2" ) // Response: Status: "Done", Resolution: "Fixed" ✅
When: Ticket closed successfully in JIRA
Action:
✅ USER STORY COMPLETION REPORT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **Ticket:** JNF-2 **Title:** [User Story Title from JIRA] **Status:** ✅ DONE (via JIRA MCP) **Resolution:** Fixed (via JIRA MCP) ## What Was Delivered [Summary of implementation] ## Metrics - 📊 Lines of Code Added: [X] - 📊 Files Modified: [X] - 📊 Tests Added: [X] - 📊 Test Coverage: [X]% - ⏱️ Total Duration: [X hours] ## GitHub Reference - Branch: feature/JNF-2 - PR: [PR number] - Commits: [X commits] - Merge Commit: [Hash] ## JIRA Ticket (via MCP) - Ticket: JNF-2 - Status: ✅ Done (via transitionJiraIssue MCP call) - Resolution: ✅ Fixed (via editJiraIssue MCP call) - URL: [Link to ticket] - Comments: ✅ 3 MCP comments added - Phase 5: Development methodology - Phase 10: PR ready for review - Phase 11: Completion & closure ## Next Steps Proceed to next user story:
I want to action user story [JNF-XX]: [Title]
Or: - [ ] Review production deployment results - [ ] Monitor for any issues - [ ] Document lessons learned --- 🚀 Story Complete! Ready for next ticket!
┌─────────────────────────────┐ │ PHASE 1: Selection │ │ User Confirms Story │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 2: Branch Creation │ │ Create feature/[TICKET_ID] │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 3: Analysis │ │ Break Down & Plan │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 4: Research │ │ Documentation & Google │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 5: JIRA Update │ │ Log methodology & plan │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 6: Development │ │ Execute tasks │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 7: Testing │ │ Unit & Manual Tests │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ PHASE 8: Approval │ │ Present to User │ └────┬────────────────────┬───┘ │ │ ✅ YES ❌ CHANGES/REVIEW │ │ ▼ ▼ ┌─────────────────────────────┐ │ PHASE 9: Commit to GitHub │ ◄──┐ │ Create PR │ │ └──────────────┬──────────────┘ │ │ │ ▼ │ ┌─────────────────────────────┐ │ │ PHASE 10: Await Merge │ │ │ Team Review & Approval │ │ └──────────────┬──────────────┘ │ │ │ ▼ │ ┌─────────────────────────────┐ │ │ PHASE 11: Completion │ │ │ Verify & Close Ticket │ │ └─────────────────────────────┘ │ │ Request Changes Return ──────┘
# Create and checkout branch git checkout -b feature/JNF-25 # Add changes git add . # Commit with message git commit -m "feat(JNF-25): add participant registration endpoint" # Push to remote git push origin feature/JNF-25 # Switch branches git checkout main
# Install dependencies pnpm install # Start development server pnpm dev # Run tests pnpm test # Run tests with coverage pnpm test:coverage # Lint and format pnpm lint --fix pnpm format
# Update ticket status JIRA: Transition issue [JNF-25] to "In Development" # Add comment JIRA: Add comment to [JNF-25] with text: "[Comment text]" # Link issues JIRA: Link [JNF-25] relates to [JNF-XX] # Search issues JIRA: Search issues in project JNF
When working through these phases, consult:
| Phase | Document | Section |
|---|---|---|
| 1 | Any | Start here |
| 3 | IMPLEMENTATION-INDEX.md | Story Components |
| 4 | COMPLETE-SUMMARY.md | Feature Matrix |
| 4 | ultimate-detailed-implementation.md | Architecture & Patterns |
| 4 | ultimate-implementation-part2.md | Service Examples |
| 6 | ultimate-implementation-part2.md | Services & Components |
| 7 | IMPLEMENTATION-INDEX.md | Testing Strategy |
| 8 | None | User decision |
| 9 | None | Standard Git workflow |
| 10 | None | JIRA update |
| 11 | COMPLETE-SUMMARY.md | Deployment info |
By completing all phases, you will have:
To action a JIRA user story, say:
"I want to action user story [JNF-XX]" (Title is optional - MCP will fetch it)
The system will:
CRITICAL: Read this first
This system automatically uses JIRA MCP (Atlassian) to:
HOW MCP INTEGRATION WORKS:
The system will:
Phase 1 (Confirmation):
Phase 5 (JIRA Update - Before Development):
Phase 10 (Await Merge):
Phase 11 (Completion):
Before using this system, ensure:
Cloud ID Configuration:
ndisapppochttps://ndisapppoc.atlassian.net/JNFCloud ID will be used automatically in all MCP calls:
cloudId: "ndisapppoc"
JIRA MCP: Get issue [JNF-2] Returns: Title, Description, Acceptance Criteria, Priority, Epic, Status, etc.
JIRA MCP: Add comment to [JNF-2] Title: "Development Methodology & Plan" Body: [Methodology, action list, research findings]
JIRA MCP: Transition [JNF-2] to "In Development"
JIRA MCP: Add comment to [JNF-2] Title: "Pull Request Created - Awaiting Review" Body: [PR Link, Testing Results, Ready for Review status]
JIRA MCP: Transition [JNF-2] to "Done" JIRA MCP: Add comment to [JNF-2] Title: "✅ COMPLETED - Merged to Production" Body: [Completion summary, metrics, delivery confirmation]
USER SAYS: ┌─────────────────────────────────────────────────┐ │ "I want to action user story JNF-2" │ └────────────────────┬────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────┐ │ SYSTEM ACTIVATES JIRA MCP │ │ - Connects to JIRA API │ │ - Fetches ticket JNF-2 data │ └────────────────────┬────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────┐ │ PHASE 1: PRESENTS REAL TICKET DATA │ │ ✅ Title: [From JIRA] │ │ ✅ Description: [From JIRA] │ │ ✅ Acceptance Criteria: [From JIRA] │ │ ✅ Priority: [From JIRA] │ │ ✅ Epic: [From JIRA] │ │ │ │ Do you want to proceed? YES / NO │ └────────────────────┬────────────────────────────┘ │ YES ◄──┴──► NO │ │ ▼ ▼ PROCEED TO REQUEST PHASE 2 DIFFERENT TICKET │ ▼ ┌──────────────────────────┐ │ PHASES 2-4: ANALYSIS │ │ (Local work) │ └──────────────┬───────────┘ │ ▼ ┌──────────────────────────┐ │ PHASE 5: JIRA MCP UPDATE │ │ ✅ Add comment │ │ ✅ Update status │ │ ✅ Link related issues │ └──────────────┬───────────┘ │ ▼ ┌──────────────────────────┐ │ PHASE 6-7: DEVELOPMENT │ │ (Local work) │ └──────────────┬───────────┘ │ ▼ ┌──────────────────────────┐ │ PHASE 8: USER APPROVAL │ └──────────────┬───────────┘ │ APPROVE ◄ │ ▼ ┌──────────────────────────┐ │ PHASE 9: PUSH TO GITHUB │ │ (Local work) │ └──────────────┬───────────┘ │ ▼ ┌──────────────────────────┐ │ PHASE 10: JIRA MCP │ │ ✅ Add PR comment │ │ ✅ Update to "In Review" │ │ ✅ Notify team │ └──────────────┬───────────┘ │ ▼ ┌──────────────────────────┐ │ PHASE 11: JIRA MCP │ │ ✅ Add completion comment│ │ ✅ Close ticket │ │ ✅ Update status to Done │ └──────────────────────────┘
SYSTEM ACTION: 1. Parse ticket ID from user input (JNF-2) 2. Call JIRA MCP: getJiraIssue(cloudId, "JNF-2") 3. Receive: { key: "JNF-2", title: "Create user authentication system", description: "...", acceptanceCriteria: [...], priority: "High", epic: "Security", status: "Backlog" } 4. Display in Phase 1 format 5. Wait for user YES/NO
SYSTEM ACTION: 1. Prepare comment with methodology & action list 2. Call JIRA MCP: addCommentToJiraIssue(cloudId, "JNF-2", comment) 3. Call JIRA MCP: transitionJiraIssue(cloudId, "JNF-2", "In Development") 4. Confirm updates in JIRA 5. Continue to Phase 6
SYSTEM ACTION: 1. Prepare comment with PR link & testing results 2. Call JIRA MCP: addCommentToJiraIssue(cloudId, "JNF-2", comment) 3. Call JIRA MCP: transitionJiraIssue(cloudId, "JNF-2", "In Review") 4. Confirm update in JIRA 5. Wait for merge approval
SYSTEM ACTION: 1. Prepare final completion comment 2. Call JIRA MCP: addCommentToJiraIssue(cloudId, "JNF-2", comment) 3. Call JIRA MCP: transitionJiraIssue(cloudId, "JNF-2", "Done") 4. Confirm closure in JIRA 5. Report completion
System Prompt Version: 1.0
Last Updated: October 19, 2025
Status: Ready for Use
To action a user story, provide:
Example:
I want to action user story JNF-25: Participant registration endpoint & UI YES - Let's proceed!
The system will handle the rest! ✨