setting-up-scrum

Provision a Sprints database and add sprint-related fields to Tasks.

3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill setting-up-scrum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setting-up-scrum
Source: https://github.com/kazukinagata/waggle/tree/main/skills/setting-up-scrum
Command: npx skills add https://github.com/kazukinagata/waggle --skill setting-up-scrum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Provisions the Sprints database and extends the Tasks DB with sprint-related fields. It is opt-in and idempotent.

Core Features & Use Cases

  • Idempotent setup that creates a Sprints (Objectives) database alongside Tasks.
  • Adds sprint-related fields to Tasks: Sprint relation, Complexity Score, and Backlog Order.
  • Updates provider config to reference the new Sprints DB and aligns with the existing Tasks DB.

Quick Start

Run the Scrum setup to provision the Sprints DB and extend Tasks with sprint-related fields.

Frequently Asked Questions about setting-up-scrum

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

FAQPage Schema
How do I set up a Sprints database for Scrum tracking in Notion?

It provisions a dedicated Sprints database alongside your existing Tasks database and updates provider config to reference the new structure automatically.

How do I add sprint-related fields like complexity and backlog order to my tasks?

It extends the Tasks DB schema by adding a Sprint relation, Complexity Score, and Backlog Order fields during the provisioning process.

Can I safely rerun Scrum database setup without duplicating my existing Notion data?

Yes, the Scrum setup is fully idempotent, so rerunning it safely checks existing configurations and extends schemas without duplicating databases or fields.

How do I link my backlog tasks to specific sprints for velocity tracking?

Linking backlog tasks to sprints is configured by adding a Sprint relation field to the Tasks database during the initial provisioning setup.

Does this Scrum setup tool work with my existing provider configuration?

It works with existing configurations by detecting the provider, aligning with the current Tasks DB, and updating the config to reference the new Sprints DB.