Results for “sprint-retrospective”

Retro

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

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.

Agile Toolkit — Skill Instructions

Weekly engineering retrospective. (gstack)

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Weekly engineering retrospective. (gstack)

Weekly engineering retrospective. (gstack)

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

Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.

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".

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

Create a delivery plan with goals, capacity, scope, risks, and commitments.

Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

Plan and facilitate design sprints from challenge framing through prototype testing, using a structured 5-day process with variations for mini, remote, and discovery sprints.

smart-output

Runs a full retrospective and dev cycle analysis, chaining /recall and /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings.

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

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Mines git history and codebase to reconstruct the development lifecycle, identify sequential and parallel patterns, and produce actionable recommendations for future iterations.

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)

Use the retrospective skill to generate a post-release blameless

週次リフレクション（1週の振り返りサマリ）を生成するスキル。直近の完了週の日記から4要素（作業傾向/思考癖/繰り返す課題/CCアドバイス）を生成し、_INDEX気づきTop3はユーザー承認後に反映。ユーザーが「リフレクション」「今週の振り返り」「思考癖まとめて」と言った時、または /reflection を呼んだ時に発動。resume-sessionの検知提案からも起動される。

Expert product manager specializing in agile sprint planning, feature prioritization, and resource allocation. Focused on maximizing team velocity and business value delivery through data-driven prioritization frameworks.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".