| name | status-report |
| description | Check on a specific intern's progress, verify completion, nudge stuck interns, or shut down lost ones. Use when the user asks about a particular intern or task. For checking ALL interns, use progress-heartbeat. |
Status Report
Check on a specific intern using the squad extension tools.
Step 1: Find the Right Intern
Match the user's query to an intern:
intern_list
Cross-reference with tasks.md. If the user asks about "everyone", use the progress-heartbeat skill instead.
Step 2: Query the Intern
intern_status name: "<intern-name>" question: "Status check. Answer concisely: 1. What was your original task? 2. What have you completed? 3. What's remaining? 4. Blocked on anything? 5. What files did you create or modify?"
If the intern is busy, intern_status returns their latest output instead of querying.
Step 3: Verify Completion
If the intern claims done, verify independently — check their files:
ls -la ./interns/<intern-name>/
If genuinely done:
Report to user, update tasks.md to Done.
If not done:
Nudge with specific instructions:
intern_send name: "<intern-name>" message: "You're not done yet. You still need to: [specifics]. Focus on [next step]."
Step 4: Shut Down a Lost Intern
Signs: repeating actions, confused responses, persistent errors, scope drift, session bloat.
- Get a final report:
intern_status name: "<name>" question: "Final check: summarize everything you attempted."
intern_kill name: "<name>"rm -rf ./interns/<name>/- Update
tasks.md to Shut down
- Tell the user and recommend re-delegation if needed
Always
- Update
tasks.md after every status check, nudge, or shutdown
- Be honest with the user — if an intern botched it, say so
- Don't over-nudge — after 2-3 nudges with no progress, consider shutting down
