Results for “sprints”

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.

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

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.

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

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

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

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

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

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

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

Retro

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting, then commit with git.

Design loading, skeleton, and progressive content reveal patterns that maintain user confidence and perceived performance.

Agile Toolkit — Skill Instructions

GSAP Skill

Simulates SSL stripping attacks using sslstrip, Bettercap, and mitmproxy in authorized environments to test HSTS enforcement, certificate validation, and HTTPS upgrade mechanisms.

sse-streaming

GPU-only SLURM scheduling for KINTSUGI: never use CPU fallback — measured speedups: stitch 25x, decon 5x, EDF 15x (~13x full cycle)

MANTIS v4.0 — Striker-Only SM Explosion Scanner. Stalker removed. Detects violent rank jumps across 50+ markets. Fast-cycling DSL. DSL exit managed by plugin runtime via runtime.yaml.

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

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.

Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack)

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Most teams run one test — expected peak for ten minutes — and believe they have

Thin orchestrator — runs capture-brief, sam-scan, and competitive-snapshot in order for a new pursuit row. Use when user wants standard admin kickoff without running three buttons manually.

Remix patterns including loaders, actions, nested routing, progressive enhancement, and deployment strategies.

Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript, covering routes, plugins, validation, error handling, authentication, testing, performance, logging, deployment, and more.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.