From vamfi-software-consultancy
This skill should be used when the user asks to "run a health check", "assess the engagement", "how healthy is this project", "retrospective", "check delivery health", "review team performance", "assess client satisfaction", or needs a structured assessment of an ongoing consulting engagement.
npx claudepluginhub vamfi/vamfi-plugins --plugin vamfi-software-consultancyThis skill uses the workspace's default tool permissions.
Assess the health of an ongoing consulting engagement across five dimensions. Produce a RAG status report, improvement backlog, and retrospective output that feeds the next cycle of delivery.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Assess the health of an ongoing consulting engagement across five dimensions. Produce a RAG status report, improvement backlog, and retrospective output that feeds the next cycle of delivery.
Regular health checks prevent engagements from quietly failing. Applied every sprint or month, this skill surfaces problems while they are still correctable and reinforces what is working.
Score each dimension: Green (on track), Amber (at risk, needs action), Red (failing, needs immediate intervention).
Questions to assess:
Evidence to gather: Sprint completion rates, velocity chart, blocker log, scope change log.
Questions to assess:
Evidence to gather: Defect counts by sprint, coverage % trend, debt register changes, incident count.
Questions to assess:
Evidence to gather: Team sentiment (1-10 quick survey), knowledge sharing activities, PR review distribution.
Questions to assess:
Evidence to gather: Stakeholder meeting notes, decision log, any escalations or complaints.
Questions to assess:
Evidence to gather: Budget tracker, forecast to complete, change request log.
# Engagement Health Report: [Engagement Name]
Date: [YYYY-MM-DD] | Reporting Period: [Sprint/Month]
## Health Dashboard
| Dimension | Status | Trend | Key Finding |
|---|---|---|---|
| Delivery | ๐ข/๐ก/๐ด | โ/โ/โ | [key finding] |
| Quality | ๐ข/๐ก/๐ด | โ/โ/โ | [key finding] |
| Team | ๐ข/๐ก/๐ด | โ/โ/โ | [key finding] |
| Relationship | ๐ข/๐ก/๐ด | โ/โ/โ | [key finding] |
| Commercial | ๐ข/๐ก/๐ด | โ/โ/โ | [key finding] |
| **Overall** | ๐ข/๐ก/๐ด | | |
## Key Findings
[3-5 bullet points on the most important findings]
## Improvement Actions
| Action | Dimension | Owner | Due | Expected Outcome |
|---|---|---|---|---|
| [action] | [dimension] | [role] | [date] | [outcome] |
Run a 4L retrospective to collect team input:
Liked: What worked well this sprint/period? Learned: What did we discover (good or bad)? Lacked: What was missing that would have helped? Longed for: What would we ideally have had?
For each item in Lacked and Longed for: produce an action item with an owner.
references/engagement-maturity-model.md โ Maturity progression from AI-Assisted to AI-Autonomousassets/health-check-template.md โ Blank health check template