compound

Consolidate sprint artifacts into a structured capitalization report with patterns and lessons.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates sprint learnings and artifacts into a structured capitalization report that identifies patterns, lessons learned, and actionable improvements across three axes.

Core Features & Use Cases

  • Isolated sub-agent with a fresh context to analyze sprint artefacts (patterns, deviations, and competencies)
  • Generates consolidated sections for Patterns, Lessons Learned, Best Practices Confirmed, and Technical Debt
  • Updates backlog and profile data as part of the capitalization workflow and can emit draft tickets for follow-up actions

Quick Start

Summarize sprint learnings by running the compound workflow at sprint end to generate a capitalization report.

Frequently Asked Questions about compound

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

FAQPage Schema
How do I consolidate sprint learnings into a structured capitalization report?

Sprint capitalization consolidates sprint artefacts into a report capturing patterns, lessons learned, best practices, and technical debt across three axes. Run the compound workflow at sprint end to generate a structured markdown analysis.

What is sprint capitalization and when do I need to analyze project learnings?

Sprint capitalization analyzes project learnings, methodology deviations, and competency updates at sprint end. It is needed when you want to systematically capture patterns and improvements from your sprint workspace artefacts into a structured report.

How do I generate draft tickets from sprint lessons learned and technical debt?

Draft tickets from sprint lessons learned are generated by optionally emitting a .gse/compound-tickets-draft.yaml file. This file contains ticket proposals for follow-up actions derived from the patterns and technical debt identified during artefact analysis.

Can I analyze methodology deviations and competency updates using my existing sprint workspace artefacts?

Yes, you can analyze methodology deviations and competency updates using your sprint workspace artefacts. An isolated sub-agent with a fresh context evaluates these artefacts to identify patterns and improvements across three axes.

What is the best way to document technical debt and best practices confirmed during an agile sprint?

The best way to document technical debt and best practices confirmed is to generate a docs/sprints/sprint-{NN}/compound.md file. This structured capitalization report isolates analysis into dedicated sections for technical debt, patterns, and lessons learned.

Does sprint capitalization work without external dependencies to update backlog and profile data?

Sprint capitalization works without external dependencies to update backlog and profile data. The workflow uses an isolated sub-agent to analyze sprint artefacts and generate capitalization reports independent of additional tools.