produce

Create per-task worktrees and feature branches for production execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates production execution by creating per-task worktrees and feature branches to isolate and track work for every task within a sprint.

Core Features & Use Cases

  • Per-task worktrees and dedicated feature branches with automated baseline capture for scope reconciliation.
  • Gate-guarded production flow: pre-production checks, backlog-driven task selection, and robust risk controls.
  • Tight integration with sprint/backlog artefacts to drive task status updates and traceability.

Quick Start

Trigger production for the next pending task by running the /gse:produce command, optionally specifying a specific task with --task or running all tasks with --all.

Frequently Asked Questions about produce

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

FAQPage Schema
How do I isolate git work for individual tasks in a sprint?

This Skill automates git worktree creation and feature branch isolation per task within a sprint. It captures baselines for scope reconciliation and updates sprint backlog artefacts to maintain traceability across the production pipeline.

What's the best way to automate backlog-driven task selection for production?

Automating backlog-driven task selection requires a gate-guarded production flow with pre-production checks. This approach drives deterministic task production while enforcing risk controls and updating task statuses automatically.

How do I run production for all pending tasks using git worktrees?

Trigger production execution by running the produce command with the --all flag. This processes all pending tasks from the backlog, creating isolated worktrees and feature branches for each task sequentially.

Can I specify a specific task for isolated worktree production?

Yes, you can specify a specific task by running the produce command with the --task flag. This targets a single pending task, creating its dedicated worktree and feature branch without processing the entire backlog.

Does sprint backlog integration work with automated git workflows?

Sprint backlog integration works directly with automated git workflows by driving task status updates and traceability. The production flow reads from backlog artefacts to select tasks and writes status changes back after completion.

When should I not use isolated git worktrees for task production?

You should avoid isolated git worktrees if your production pipeline lacks defined sprint or backlog artefacts. The workflow requires backlog-driven task selection and sprint integration to enforce guardrails and traceability effectively.