plan

Select backlog items and generate the .gse/plan.yaml for sprint planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan sprints by selecting backlog items and generating the .gse/plan.yaml, enabling coherent scope, budgeting, and task coordination across abstractions.

Core Features & Use Cases

  • Strategic and tactical planning modes to create sprint plans and refine tasks from the backlog.
  • Cross-cutting workflow management that updates plan.yaml, coordinates with backlog.yaml, and tracks budget and status transitions.
  • Real-world scenario: a product team iterates on a sprint by choosing high-priority backlog items and drafting the plan to guide development, testing, and review.

Quick Start

Initialize a sprint plan by selecting backlog items and generating the .gse/plan.yaml for the current sprint.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a sprint plan from my existing backlog?

Sprint planning is handled by selecting backlog items and outputting a .gse/plan.yaml file. This coordinates scope, budget, and task dependencies across your agile workflow.

What is the difference between strategic and tactical planning modes for sprints?

Strategic planning mode creates high-level sprint plans, while tactical mode refines specific tasks from the backlog into the plan.yaml. Both modes enforce budget checks and coordinate with backlog.yaml and status.yaml files.

Does sprint planning work with existing backlog and status YAML files?

Yes, sprint planning integrates directly with existing backlog.yaml and status.yaml files. It updates the plan.yaml while reading backlog items and tracking status transitions to maintain coherent task coordination.

How do I track budget and task dependencies during sprint planning?

Budget and task dependencies are tracked automatically during sprint planning by enforcing checks within the generated .gse/plan.yaml. This ensures scope and budget constraints are respected across strategic and tactical modes.

What is the best way to align backlog items with sprint execution?

The best way to align backlog items with sprint execution is generating a .gse/plan.yaml that bridges the two. This enforces budget checks and status transitions, linking the backlog directly to execution guidance.