evolve-unit

Apply categorized feedback to editorial units while preserving DZ-ref tags.

Updated Mar 21, 2026

Search Tags:#traceability #pedagogy #quality-assurance #review-feedback #evolve #editorial-unit #dz-ref

Ready to run

npx skills add https://github.com/JaviMontano/prolipa-plugins --skill evolve-unit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evolve-unit
Source: https://github.com/JaviMontano/prolipa-plugins/tree/main/scriba/skills/evolve-unit
Command: npx skills add https://github.com/JaviMontano/prolipa-plugins --skill evolve-unit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evolution of editorial units without traceability creates drift in curriculum alignment and learning outcomes. This skill ensures revisions preserve the DZ-ref thread and maintain pedagogical structure during iterative feedback cycles.

Core Features & Use Cases

Preserve DZ-ref tags while applying feedback
Categorize feedback by type (PEDAGOGICAL, STRUCTURAL, CONTENT, STYLE, COMPREHENSIBILITY) and prioritize CRITICAL changes
Generate an explicit evolution report with change logs, conflict resolutions, and validation status
Validate post-evolution integrity for taxonomy, coverage, and style

Quick Start

Provide the updated unit and a complete evolution report by applying all approved feedback.

Frequently Asked Questions about evolve-unit

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

FAQPage Schema

How do I iteratively improve editorial units while preserving curriculum traceability?▼

Iterative editorial unit improvement preserves curriculum traceability by applying feedback across pedagogical, structural, content, and style dimensions while keeping DZ-ref tags intact. This approach prevents curriculum alignment drift and maintains learning outcome consistency during revision cycles.

What is the best way to apply review feedback to an editorial unit without losing taxonomy alignment?▼

Applying review feedback without losing taxonomy alignment requires categorizing feedback by type (PEDAGOGICAL, STRUCTURAL, CONTENT, STYLE, COMPREHENSIBILITY) and prioritizing CRITICAL changes. Post-evolution validation then ensures taxonomy, coverage, and style integrity remain intact.

How does feedback evolution handle conflict resolutions in pedagogical content?▼

Feedback evolution handles conflict resolutions by generating an explicit evolution report after applying approved changes. This report documents the change log, details how conflicting feedback was resolved, and confirms the post-validation status of the revised unit.

Can I categorize review feedback by type when updating educational content?▼

Review feedback can be categorized by type when updating educational content into PEDAGOGICAL, STRUCTURAL, CONTENT, STYLE, and COMPREHENSIBILITY classifications. This categorization allows targeted revisions and prioritization of CRITICAL changes within the Scriba workflow.

When do I need to validate post-evolution integrity for educational units?▼

Post-evolution integrity validation for educational units is needed immediately after applying feedback revisions. It checks taxonomy alignment, curriculum coverage, and style consistency to ensure the evolved unit maintains its pedagogical structure and DZ-ref traceability.