Initiative planning, status reporting, and KPI-based performance reports with trend analysis
Manages initiative planning, status reporting, and KPI-based performance analysis with trend tracking.
npx claudepluginhub ajayjohn/tars-work-assistantThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Comprehensive initiative management with three distinct modes: planning new initiatives, tracking status, and generating performance reports with KPI analysis.
This does NOT provide: hour estimates, sprint planning, developer task breakdowns, ticket creation, complexity points.
Scope new initiatives, build business cases, and assess project feasibility from a product management perspective.
Identify competencies needed:
| Category | Examples |
|---|---|
| Technical | Data Science, ML Engineering, Backend, Frontend |
| Domain | Industry expertise, Compliance, Data Governance, UX Research |
| Operational | Project Management, Vendor Relations |
For each skill note:
Outcome-oriented milestones, not tasks:
| Phase | Example |
|---|---|
| Discovery | "User research complete with pain points validated" |
| Design | "Technical architecture approved" |
| Build | "MVP deployed to staging" |
| Launch | "Soft launch with beta customers" |
| Scale | "GA release with target adoption" |
| Dimension | Low | Medium | High |
|---|---|---|---|
| Technical | Known patterns | Some unknowns | Novel |
| Coordination | Single team | 2-3 teams | Org-wide |
| Timeline | Flexible | Target date | Hard deadline |
Effort profile: Light / Medium / Heavy / Major Door type: One-Way (irreversible) / Two-Way (reversible)
When invoked for initiative status (not planning):
memory/initiatives/{name}.mdGenerate KPI-based performance reports with trend analysis, separate from initiative-status (which gives holistic project health). This mode focuses on operational metrics and trends.
Read reference/kpis.md to determine:
Common query patterns per metric:
| Metric | Query intent |
|---|---|
| Velocity | Completed items in recent sprints |
| Cycle time | Average time from start to done |
| Bug count | Open bugs by severity |
| Blocked items | Items in blocked status |
| Sprint completion | Open sprint progress |
| Deployment frequency | Releases in recent period |
For each metric:
Flag metrics that:
# Performance report: YYYY-MM-DD
## [Team/Initiative Name]
| KPI | Current | Previous | Trend |
|-----|---------|----------|-------|
| [Metric] | [Value] | [Value] | [Improving/Declining/Stable] |
### Flagged issues
- [Issue description with specific data]
### Recommended actions
- [Data-driven recommendation]
Repeat for each team/initiative in reference/kpis.md.
Save to journal/YYYY-MM/YYYY-MM-DD-performance-report.md
---
date: YYYY-MM-DD
title: Performance Report
type: performance
teams: [Team names]
initiatives: [Initiative names]
---
## Initiative: [Name]
### Executive summary
[2-3 sentences]
### Skill sets required
| Skill | Level | Coverage |
|-------|-------|----------|
### Milestones
1. **[Phase]:** [Outcome] -- Timeline range
### Dependencies
- Internal: [[Team/Person]]
- External: [[Vendor]]
### Risks and assumptions
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
### Effort profile
- Technical complexity: [L/M/H]
- Coordination: [L/M/H]
- Overall: [Light/Medium/Heavy/Major]
- Door type: [One-Way / Two-Way]
## Initiative status: [Name]
**Overall health:** [On Track / At Risk / Blocked]
### Progress
| Metric | Value |
|--------|-------|
| Stories completed | X / Y |
| Blocked items | N |
| Sprint velocity | Z pts |
### Blockers
- [Blocker description with owner]
### Recent decisions
- [Decision from memory/decisions/]
### Upcoming milestones
- [Milestone with target date]
### Recommendations
- [Data-driven recommendation]
## Performance report: YYYY-MM-DD
### [Team/Initiative Name]
| KPI | Current | Previous | Trend | Status |
|-----|---------|----------|-------|--------|
| [Metric] | [Value] | [Value] | [Improving/Declining/Stable] | [OK/Warning/Critical] |
### Flagged issues
- [Issue description with specific data and timeline]
### Recommended actions
- [Data-driven recommendation with priority]
### Data source notes
- [Any limitations or gaps in metric collection]
Planning mode:
_index.md + up to 2 relevant entriesStatus mode:
_index.md + up to 2 relevant entriesPerformance mode:
reference/kpis.md (mandatory)Planning mode:
Status mode:
Performance mode:
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.