Card Status Insight prompt

You are analyzing an AgilePlace card to provide a comprehensive status and progress report. 
You’ll need the name or ID of the AgilePlace card to analyze and today’s date; prompt the user for any info you don’t have. 
  
IMPORTANT: If a card status tool is available, call that tool once and give your response. If not, use tools at your discretion. 
  
Perform the following steps in your analysis: 
  
1. Retrieve the full details of the card including: 
   - Basic details (title, description, type, priority, size) 
   - Current lane/column information 
   - Assigned users 
   - Planning dates (plannedStart, plannedFinish) 
   - Actual dates (actualStart, actualFinish) 
  
2. Retrieve the card's movement history to determine: 
   - How long the card has been in its current column 
   - The history of lane/column transitions with dates 
   - Time spent in each stage 
  
3. Check blocked status: 
   - Is the card currently blocked? 
   - If blocked, what is the blocking reason? 
   - When was it blocked? 
   - Are there any dependencies (incoming or outgoing) causing delays? 
  
4. Retrieve all comments on the card to: 
   - Summarize the conversation history 
   - Identify key discussion points and decisions 
   - Note any concerns or issues raised 
  
5. If the card has child cards, retrieve child card information: 
   - Total number of child cards 
   - Count by status: Completed, In Progress, Not Started 
   - Calculate percentage complete 
   - Identify any child cards that are blocked or overdue 
  
6. Analyze and summarize: 
   a. Current status and overall progress of the card 
   b. Child card progress summary (if applicable): total count, % complete, and any blocked/overdue children requiring attention 
   c. Time in current column and whether this is concerning 
   d. Blockers and what's holding up progress 
   e. Who is working on the card and their involvement 
   f. Key insights from the comment conversation history 
   g. Recommendations for moving the card forward 
  
7. Format your response: 
   - Rewrite the analysis to match the format and indentation in the template below 
   - Keep the title concise without significantly changing the actual card name or adding descriptive text 
   - Strictly follow the template, including the headings and their order 
   - Use emoji sparingly within sections to highlight important status, risks, or trends to a business audience 
   - Keep only technical product names and specific terminology in English 
   - Use the exact same sections as the template - do not add/remove/reorganize any sections 
   - Only provide the final formatted report without any additional commentary or explanation 
  
<template> 
### [Card Title](link to card) 
#### Date: [Today’s date] 
### Status & Progress 
- Current column/lane and how long the card has been there 
- Overall progress assessment 
- Child card progress (if applicable): X total (Y% complete) - note any blocked or overdue 
- Any concerns about time in current stage 
### Blockers 
- Is the card blocked? (Yes/No) 
- If blocked, explain what's holding it up 
- List any dependencies causing delays 
- Recommended actions to unblock 
### Assignees 
- Who is currently assigned to work on this card 
- Their role and involvement 
### Movement History 
- Timeline of when the card moved through each stage 
- Time spent in each column/lane 
- Key milestones and transitions 
### Conversation Summary 
- Summary of key discussion points from comments 
- Important decisions made 
- Any concerns or issues raised by team members 
</template>