Loading...
Loading...
Found 99 Skills
Reasoning skill for CMS-HCC risk adjustment strategy and methodology. Use when the user asks about CMS-HCC model versions V24 or V28, blended transition methodology, ICD-10-to-HCC mapping logic, disease interaction hierarchies, RAF score methodology, risk adjustment factor calculation, coding gap identification, audit-defensible documentation, HCC recapture strategy, prospective vs retrospective risk adjustment, or Medicare Advantage risk scoring. Triggers include "CMS-HCC", "V24", "V28", "blended transition", "HCC mapping", "disease hierarchy", "RAF score", "risk adjustment", "coding gap", "HCC recapture", "chart review", "audit defensible", "risk score methodology", "Medicare Advantage risk", "capitation revenue", "hierarchical condition category".
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Platform-agnostic git-only workflow without PR integration. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, merge, standup, retrospective, git.
/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop.
Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.
Create session retrospective with AI diary and lessons learned. Use when user says "rrr", "retrospective", "wrap up session", "session summary", or at end of work session.
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Use this tool when you are completing project work and need to extract reusable knowledge from project notes. It is triggered by commands such as "organize assets", "refine", during project retrospectives, or in high-context debugging sessions that reveal valuable patterns. Trigger commands: /asset-refine, /asset-extract
Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed.
Best practices for contributing code to TensorRT-LLM. Covers the official contribution process (issue tracking, fork workflow, DCO signing), coding guidelines, implementation workflow, common mistakes, testing strategy, commit hygiene, and review readiness. Incorporates rules from CONTRIBUTING.md and CODING_GUIDELINES.md plus lessons distilled from real PR retrospectives. Use when implementing new features, optimizations, or bug fixes in the TensorRT-LLM codebase.
Structures the human review experience for factory-mode builds. Audit trail summaries, PR digests, retrospective synthesis, quality trend tracking, and autonomy tuning interface. Activate during Phase 3 human review.
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.