sprint

Name: sprint
Availability: InStock
Author: Forgeplan

Orchestrate multi-agent feature sprints with wave-based execution and evidence capture.

3|Updated Apr 3, 2026

Search Tags:#project planning #team collaboration #artifact management #sprint #feature execution

Ready to run

npx skills add https://github.com/ForgePlan/marketplace --skill sprint-forgeplan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/fpl-skills/skills/sprint
Command: npx skills add https://github.com/ForgePlan/marketplace --skill sprint-forgeplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires forgeplan, mcp__forgeplan__*, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates efficient execution of large features or refactor tasks by dividing them into manageable waves, assigning agents, and automating communication and evidence capture.

Core Features & Use Cases

Wave-based Execution: Divide a large task into smaller, parallelizable waves.
Agent Assignment: Dynamically assign agents to specific tasks within each wave.
Automated Evidence Capture: Capture and record evidence of work completed at the artifact level.
Use Case: Ideal for complex features or refactor sprints that require coordination among multiple team members.

Quick Start

Use the sprint skill to start a new sprint for a feature 'feature-x'.

Frequently Asked Questions about sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multi-agent feature execution for complex refactoring tasks?▼

Multi-agent feature execution is managed by dividing large tasks into parallelizable waves, dynamically assigning agents to specific tasks, and automating communication. This approach streamlines complex refactoring by orchestrating the sprint with automated planning.

What is wave-based execution in project planning?▼

Wave-based execution in project planning divides a large feature or refactor task into smaller, manageable, and parallelizable waves. It allows teams to execute complex sprints incrementally rather than handling the entire feature simultaneously.

How do I start a sprint for a new feature?▼

To start a sprint for a new feature, you use the sprint skill to initialize the process. It requires a well-defined project context, team structure, and artifact management to orchestrate both full sprints with research phases and lightweight wave executions.

Does automated evidence capture work with artifact management during a sprint?▼

Automated evidence capture works directly with artifact management by recording evidence of completed work at the artifact level. It ensures all task outputs within the assigned waves are systematically captured and documented during the sprint.

What do I need to set up before coordinating team collaboration for a feature sprint?▼

Before coordinating team collaboration for a feature sprint, you need a well-defined project context and an established team structure. These prerequisites ensure the sprint skill can effectively orchestrate agents and manage artifacts across the execution waves.

When should I use a full sprint with research phase instead of lightweight wave execution?▼

A full sprint with a research phase is used for complex features requiring preliminary investigation, while lightweight wave execution suits straightforward refactor tasks. Both require project context and team structure to properly orchestrate multi-agent collaboration.