plan

Select backlog items and generate sprint plans in .gse/plan.yaml.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill plan-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/plan
Command: npx skills add https://github.com/tjisousa/gensem --skill plan-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The plan skill helps teams select backlog items and generate or update the living sprint plan in .gse/plan.yaml, aligning scope with budget and workflow.

Core Features & Use Cases

  • Strategic sprint planning: select items from backlog to form a new sprint plan.
  • Tactical planning: adjust scope, reorder, or refine items within the active plan.
  • Plan persistence and traceability: creates and persists .gse/plan.yaml; integrates with backlog.yaml and status.yaml for budget and sprint state.

Quick Start

Run the plan skill to generate or update the current sprint plan in .gse/plan.yaml.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan sprint backlog items into a coherent delivery scope?

Sprint planning selects backlog items and generates a living sprint plan in .gse/plan.yaml, aligning scope with budget and cross-team workflow guardrails for streamlined delivery.

What is the best way to adjust scope within an active sprint plan?

Tactical sprint planning adjusts scope by reordering or refining items directly within the active plan, updating the .gse/plan.yaml file to maintain traceability and workflow governance.

Does sprint planning require a specific backlog file format to work?

Sprint planning integrates with backlog.yaml for item selection and status.yaml for sprint state, requiring these files to enforce budget tracking and support plan persistence.

Can I use sprint planning for multi-mode coordination across teams?

Multi-mode sprint planning supports cross-team coordination and budget enforcement, applying strategic sprint creation and tactical adjustments within the GSE-One workflow.

Why does sprint planning persist data in a YAML file?

Sprint planning persists data in .gse/plan.yaml to create a living, traceable plan that integrates with backlog and status files for continuous budget enforcement and status tracking.