Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

klum-review-release

Estrellas3

Forks0

Actualizado18 de julio de 2026 a las 10:09

Reconcile KlumAST 4.0 issue curation against the repository, merged work, CI, ADRs, migration guidance, and release notes. Use for periodic release-scope reviews, API-freeze readiness, blocker analysis, and safe deferral recommendations.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

klum-dsl

klum-dsl/klum-ast

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

build-domain-first-schema

klum-dsl/klum-ast

Build a domain-first KlumAST Schema. Use when a Domain API Developer and Schema Developer want to model a domain independently of downstream targets, decide between Layer 3 and direct-schema, define DSL Object boundaries, and prove the resulting completed model with an API-only client and executable test.

2026-07-203

build-target-contract-schema

klum-dsl/klum-ast

Build a KlumAST authoring Schema for an authoritative external contract. Use when an adopter is replacing or simplifying Helm values, another configuration document, or a target-specific API contract while keeping that contract authoritative.

2026-07-203

feature-advisor

klum-dsl/klum-ast

Advise on applicable KlumAST features in an existing Schema or configured model. Use when an adopter wants a ranked, evidence-based KlumAST improvement review, an explanation of supported 4.x features that fit their model, or selected, validated model improvements.

2026-07-203

author-klum-model

klum-dsl/klum-ast

Author a configured KlumAST model. Use when a Model Writer wants to turn a representative configuration into a KlumAST model, add validation, construct it through the generated DSL, or create an executable model test.

2026-07-203

start-klum-project

klum-dsl/klum-ast

Start or adapt a Gradle project for KlumAST. Use when an adopter wants to scaffold a KlumAST project, add KlumAST to an existing Gradle build, choose domain-first or target-contract modeling, choose Layer 3 or direct-schema structure, or verify a first schema build.

2026-07-203

work-orchestrator

klum-dsl/klum-ast

Maintain a compact, evidence-backed horizon of user-selectable repository work; create and reconcile user-visible tasks without confusing completed execution with delivered repository state.

2026-07-203

name	klum-review-release
description	Reconcile KlumAST 4.0 issue curation against the repository, merged work, CI, ADRs, migration guidance, and release notes. Use for periodic release-scope reviews, API-freeze readiness, blocker analysis, and safe deferral recommendations.

Review the KlumAST Release

Produce the smallest coherent 4.0 scope consistent with accepted decisions and current implementation.

Reconcile reality

Read AGENTS.md, CONTEXT.md, docs/agents/issue-tracker.md, docs/agents/feature-triage.md, docs/agents/pull-requests.md, all curation files, open issues and milestones, recent merged PRs, current CI status, CHANGES.md, README.md, wiki/Builder-First-Migration.md, and relevant ADRs and implementation notes.

Cross-check every curation claim against current GitHub and repository state. Identify:

remaining 4.0 blockers and dependency order
decisions required before generated/public API freeze
compatibility, migration, and documentation gaps
stale or contradicted curation entries
completed, duplicate, obsolete, or superseded issues
safe deferrals to 4.1, later 4.x, or 5.0
recorded feature need horizons and workaround viability that materially affect priority
risks in implementation order and release scope

Treat green CI as evidence of tested state, not proof that unresolved product or compatibility decisions are complete. Treat feature use-case classification as priority evidence rather than an automatic ranking. Do not require a retroactive classification pass over already-triaged issues; use the record when present or when an issue is revisited for another reason.

Update analysis artifacts

During analysis, update only:

docs/implementation/issue-curation/release-4.0.md
related files under docs/implementation/issue-curation/

Record evidence, recommendation, owner/decision needed, and next action for each blocker. Keep accepted facts separate from proposed scope changes.

Propose external changes

Present proposed changes to wiki/Roadmap.md, CHANGES.md, milestones, labels, and GitHub issues separately. Apply them only after explicit maintainer confirmation and through the appropriate repo-specific skill.

Finish only when the issue index, release plan, repository state, and GitHub state reconcile; every 4.0 item has a disposition and evidence; and the recommended scope states its blockers, deferrals, and residual risks.