skills.rest
l3ocho
l3ochoCOMMUNITY
Explore all skills by this author →
GitHub

sprint-approval

Gate sprint execution behind formal approvals with milestone-based verification.

Updated Jan 26, 2026
Search Tags:#workflow#orchestrator#approval#sprint#gate#milestone
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill sprint-approval
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-approval
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/sprint-approval
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill sprint-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Approval gate logic prevents sprint execution until explicit authorization is recorded, reducing the risk of unapproved changes.

Core Features & Use Cases

  • Approval request workflow: Planner triggers an approval request after creating issues; Orchestrator verifies approval before execution.
  • Recording and verification: Update milestone with approval details; Orchestrator checks milestone for required approval details.
  • Scope enforcement & re-approval: Enforces approved scope; re-approve when scope changes.

Quick Start

Configure the sprint approval gate and ensure milestones contain explicit approval before sprint execution.

Frequently Asked Questions about sprint-approval

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

FAQPage Schema
How do I gate sprint execution behind formal approvals in an orchestration workflow?▼

Sprint approval gates enforce scope constraints by requiring re-approval when scope changes. If the approved scope is modified, the system triggers a new planner-initiated approval request before execution can proceed.

How does an approval gate handle emergency sprint starts?▼

Sprint approval gates provide an emergency start option for bypassing the standard approval workflow. This allows execution to proceed urgently while still maintaining governance records within the orchestration workflow.

What is the best way to record approval details for sprint milestones?▼

The best way to record approval details is to update the sprint milestone with explicit authorization data after a planner triggers an approval request. The orchestrator then checks this milestone for required approval details before execution.

Can I enforce approved scope constraints and trigger re-approval for sprint planning?▼

Yes, sprint approval gates enforce approved scope constraints automatically. When scope changes occur during sprint planning, the system requires re-approval before the orchestrator can proceed with execution.

Why does my orchestrator verify milestone approval details before starting a sprint?▼

An orchestrator verifies milestone approval details before starting a sprint to prevent unapproved changes. This governance mechanism ensures explicit authorization is recorded in the milestone, reducing execution risk.

Related Skills

Explore More Product & Management Skills→
Adelie-SquadAdelie-Squad
17

Scope Estimator Agent

Clarify feature scope and generate WBS, sprint, and risk buffer documents.

Official
Advanced
sunholo-datasunholo-data
33

AILANG Sprint Executor

Execute approved sprint plans with test-driven development and lint checks.

Official
Intermediate
duongtdnduongtdn

status

Aggregate local sprint files and GitHub issue data into a status report.

Community
Advanced
dbrijeshdbrijesh

review-gates

Manage structured human review checkpoints for code, security, architecture, and database changes.

Community
Advanced