sprint-plan

Generate sprint planning artifacts and analyze previous sprint outcomes.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/ASTRA-TECHNOLOGY-COMPANY-LIMITED/astra-methodology --skill sprint-plan-astra-technology-company-limited
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/ASTRA-TECHNOLOGY-COMPANY-LIMITED/astra-methodology/tree/main/skills/sprint-plan
Command: npx skills add https://github.com/ASTRA-TECHNOLOGY-COMPANY-LIMITED/astra-methodology --skill sprint-plan-astra-technology-company-limited

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of essential sprint planning artifacts, ensuring a structured and efficient start to each development cycle.

Core Features & Use Cases

  • Automated Artifact Generation: Creates prompt maps, progress trackers, and retrospective templates.
  • Sprint Initialization: Streamlines the process of setting up a new sprint, including carryover analysis.
  • Use Case: Kick off a new development sprint by having the AI automatically generate all necessary planning documents, analyze previous sprint outcomes, and prepare for the planning meeting.

Quick Start

Use the sprint-plan skill to initialize a new sprint, automatically determining the next sprint number if not provided.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I automate sprint planning and carryover analysis for a new development cycle?

Sprint planning automation initializes a new development cycle by generating a prompt map, progress tracker, and retrospective template. It analyzes previous sprint outcomes, including incomplete features and unaddressed actions, to inform the new sprint's structure and carryover tasks.

What is a prompt map in agile sprint planning?

A prompt map in agile sprint planning is an artifact generated to guide the development cycle. It is automatically created alongside a progress tracker and retrospective template to provide a structured approach for managing tasks and unaddressed actions.

Can I automatically determine the next sprint number from existing documentation?

Yes, you can automatically determine the next sprint number. The sprint initialization process checks existing documentation and automatically assigns the next sprint number if one is not explicitly provided by the user.

How do I track incomplete features and unaddressed retrospective actions across sprints?

You track incomplete features and unaddressed retrospective actions by analyzing previous sprint outcomes during initialization. The process evaluates partially completed tasks and generates a retrospective template to ensure carryover tasks inform the new sprint.

Does automated sprint planning work without manual setup for retrospective templates?

Yes, automated sprint planning works without manual setup for retrospective templates. The process automatically generates the retrospective template along with the prompt map and progress tracker when initializing the new sprint.