Results for “sprints”

Interact with Jira issues, sprints, and workflows through a CLI or MCP backend, with safety checks and approval gates.

Interact with Atlassian Jira via REST API, JQL, workflow transitions, sprints, and webhooks for issue tracking and project management.

Tracks Jira issues, projects, and sprints via the Atlassian API, including discovery, JQL search, transitions, and worklog management.

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.

Validate product opportunities, map assumptions, plan discovery sprints, and test problem-solution fit before committing delivery resources.

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

Analyze sprint data with Python scripts for velocity forecasting, health scoring, and retrospective insights to coach agile teams.

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.

Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.

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.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

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.

Plans sprints, breaks user stories into tasks, and estimates story points from BA and TechLead artifacts, producing sprint plan, task breakdown, and story point files.

Generates on-brand interfaces and assets for Sprintable, from throwaway HTML prototypes to production code, using the included design tokens, fonts, and UI kit components.

Facilitates structured sprint retrospectives, analyzing team feedback and sprint data to generate prioritized, actionable improvement items.

Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"

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

Team lead agent — sprint planning, standups, velocity, impediments, team health

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

Train or fine-tune sentence-transformers models for retrieval, similarity, clustering, classification, and reranking, with support for bi-encoders, cross-encoders, and sparse encoders.

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.

Coaches runners with training plans, pace calculations, race strategies, and form analysis

Query and manage Strava fitness data including activities, athlete stats, segments, routes, clubs, and gear via the strava CLI.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

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.

Coordinates sprint planning, delivery tracking, experiment management, knowledge management, and changelog governance across project management workflows.

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.