luisburgos-skills

Measure a cycle against the goals it started with, score the estimates that were made, and close the cycle by appending to history.

Collect what actually happened in a cycle — git across the configured repos, plus an optional task export — into the cycle's primary record.

One-time setup for cycle tracking — writes the config and an empty history so the first cycle can begin.

Draft curated GitHub Release notes for an existing tag — themed sections, PR and commit references, a collapsible full commit list, a compare link — as a draft the user approves before it goes public. Use when the user wants to cut a GitHub release, write notes for a tag or version, publish a release page, or has just bumped and tagged a version. Also use to rewrite an existing release's thin notes. This is the GitHub Releases page — not Play Store or TestFlight store copy, which is a separate concern with character limits and per-locale files.

Name a new skill, or audit existing skill names against this repo's taxonomy. Use when choosing what to call a skill or renaming one, or when checking a tree of skills for naming drift. Also use when another skill needs the taxonomy to justify a name it is producing.

Set the coming cycle's goals — draft 3 to 5 goals with theory and practice confidence estimates, carry or drop what did not land, and force a decision on anything unlikely to actually happen. A thin facade over setting-cycle-goals.

Close out a finished cycle's record — collect what happened into the primary record, then optionally write the readable review. A thin facade over collecting-cycle-data and writing-cycle-review.

Close a finished cycle against the goals it started with — judge each goal, score the estimates, write the assessment, and freeze the cycle into history. A thin facade over assessing-cycle-goals.

Read across many cycles for the patterns a single cycle cannot show — carried goals, estimate calibration, and gaps in the record.

Draft the next cycle's goals, each with the plan that would produce it and theory and practice confidence estimates of that plan, and force a decision on any goal you are unlikely to actually do.

The shared model of the weekly cycle — the sequence, the artifact contract, and the rules every cycle skill obeys. Read before running any of them.

Write the readable narrative of a cycle — charts and prose over the collected data, for the person who lived it.