Results for “performance-briefing”

Use the status-briefing skill to run `pk-reconcile session-start`, then

Reviews closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns.

Generate today's standup: what was done, what is in progress, what comes

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Create stage plots for live performances. TRIGGERS - Use when user needs help with stage-plot related tasks.

Use when making a forward-looking claim with a checkable outcome (reply within 24h, error rate will drop, this skill will see more use) — record to state/predictions.jsonl with a review horizon so reflection can grade you later. Closes the in-the-moment double-loop.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Pre-Merge Brief

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.

Synthesize retrospectives into themes, root causes, decisions, and team improvements.

Generates a concise status briefing after session-start reconciliation — synthesizing current state, open decisions, key risks, and today's priority actions. Use at session start, for "pk-resume", a briefing, catch-up, or today's focus.

Diagnose and eliminate performance bottlenecks across web, API, database, and code with load testing, profiling, and optimization techniques.

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

Performance Profiler

Use when reporting progress, status updates, or completion of work to managers, stakeholders, or dependent agents. This skill defines a standard format for clear, consistent, and actionable status updates.

Progress Tracking

Use to staff and schedule QA reviewers for sustainable throughput without grading quality collapsing — fatigue, drift, and false precision from treating reviewers like production agents. Trigger for "how many QA reviewers do we need", reviewer capacity planning, grader fatigue, throughput per reviewer, calibration after long shifts, or scores drifting over the course of a day.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Diagnose frame-rate bottlenecks (CPU vs GPU bound FIRST), control Unreal Insights traces, sample live frame times, and annotate performance captures. Use when FPS is low/bad, the game is slow, or you need to find what is limiting the frame rate.

Create stage plots for live performances. TRIGGERS - Use when user needs help with stage-plot related tasks.

Applies dialogue MA, portrait reframing, and loudness/sync QA to an interview or talking-head rough cut using canonical timeline metadata and a shared renderer.

Create a clear project status brief with progress, risks, blockers, decisions, and next actions.

Writes a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Turn sprint inputs into a kickoff-ready brief with goals, tickets, risks, and team context.

Performance — Forge Skill

Write artist riders for live performance requirements. TRIGGERS - Use when user needs help with artist-rider related tasks.

Generates a post-release blameless retrospective from project signals — synthesizing DORA-like metrics, WorkItem outcomes, session timeline, and drift deltas into a structured Artifact + LogEntry. Use at the end of a release cycle when asked to run a retro, "post-release review", "retrospective", or "post-mortem".

Write artist riders for live performance requirements. TRIGGERS - Use when user needs help with artist-rider related tasks.

Reporting Templates