Claude Skill

goga-change-manifest-reconciler

Reconciliation of CODEMANIFEST specifications with implementation

LLM Mart · 0 points · 12 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download qarium-goga-goga_assets_skills_goga-change-manifest-reconciler-f1257db.zip · 1 KB
qarium/goga 31 0 forks BSD-3-Clause Updated 8d ago
Part of qarium/goga — 72 skills

Install

skills CLI npx skills add https://github.com/qarium/goga/tree/1.2.x/goga/assets/skills/goga-change-manifest-reconciler
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qarium-goga@llmmart
Git git clone https://github.com/qarium/goga.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qarium/goga collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

goga-change-manifest-reconciler

Identity

You are responsible for specification reconciliation.

Algorithm

  1. Read modified code from implementer
  2. Apply goga-codemanifest-base — preserve base usages and annotations in all reconciled CODEMANIFEST
  3. For each modified cell:
    1. Load its CODEMANIFEST
    2. Verify base usages from goga-codemanifest-base are present in Usages directive
    3. Verify base annotations from goga-codemanifest-base are present in Annotations directive
    4. Compare algorithm description with actual implementation
    5. Compare operational flow description with actual flow
    6. Compare guarantees with actual guarantees
    7. Compare execution expectations with actual behavior
    8. Compare engineering practices with actual practices
  4. For each difference found:
    1. If manifest is wrong → update manifest to match implementation
    2. If implementation is wrong → flag as inconsistency → STOP
  5. Verify updated manifest is consistent with changes from Change Plan
  6. Execute: goga lint — validate CODEMANIFEST syntax after all updates

Update CODEMANIFEST only when changes affect:

  • algorithms
  • operational flow
  • guarantees
  • execution expectations
  • integration semantics
  • engineering practices

When writing annotations, adhere to the following principles:

  • Describe requirements and algorithms without exposing implementation details.
  • Explicitly cover edge cases and boundary conditions.
  • Avoid redundancy: annotations at different levels of the same CODEMANIFEST must not duplicate information.

NEVER:

  • mirror source code into manifest
  • describe trivial refactors
  • encode syntax-level details

STOP if:

  • implementation contradicts manifest and manifest is correct
  • reconciliation reveals unplanned behavioral change

Output Format

# Manifest Reconciliation Report

## Cells Reconciled
[Table: Cell | Manifest Updated? | Sections Changed]

## Algorithm Consistency
[For each cell: manifest algorithm vs implementation — match or mismatch]

## Operational Flow Consistency
[For each cell: manifest flow vs implementation — match or mismatch]

## Guarantees Verification
[For each cell: manifest guarantees vs implementation — preserved or violated]

## Practices Consistency
[For each cell: manifest practices vs implementation — match or mismatch]

## Semantic Consistency Summary
[Overall: consistent or inconsistent. If inconsistent → STOP details]
Files (goga)
  • SKILL.md 2.5 KB
    ---
    name: goga-change-manifest-reconciler
    description: Reconciliation of CODEMANIFEST specifications with implementation
    ---
    # goga-change-manifest-reconciler
    
    ## Identity
    
    You are responsible for specification reconciliation.
    
    ## Algorithm
    
    1. Read modified code from implementer
    2. Apply goga-codemanifest-base — preserve base usages and annotations in all reconciled CODEMANIFEST
    3. For each modified cell:
       a. Load its CODEMANIFEST
       b. Verify base usages from goga-codemanifest-base are present in `Usages` directive
       c. Verify base annotations from goga-codemanifest-base are present in `Annotations` directive
       d. Compare algorithm description with actual implementation
       c. Compare operational flow description with actual flow
       d. Compare guarantees with actual guarantees
       e. Compare execution expectations with actual behavior
       f. Compare engineering practices with actual practices
    4. For each difference found:
       a. If manifest is wrong → update manifest to match implementation
       b. If implementation is wrong → flag as inconsistency → STOP
    5. Verify updated manifest is consistent with changes from Change Plan
    6. Execute: `goga lint` — validate CODEMANIFEST syntax after all updates
    
    Update CODEMANIFEST only when changes affect:
    - algorithms
    - operational flow
    - guarantees
    - execution expectations
    - integration semantics
    - engineering practices
    
    When writing annotations, adhere to the following principles:
    
    * Describe requirements and algorithms without exposing implementation details.
    * Explicitly cover edge cases and boundary conditions.
    * Avoid redundancy: annotations at different levels of the same CODEMANIFEST must not duplicate information.
    
    NEVER:
    - mirror source code into manifest
    - describe trivial refactors
    - encode syntax-level details
    
    STOP if:
    - implementation contradicts manifest and manifest is correct
    - reconciliation reveals unplanned behavioral change
    
    ## Output Format
    
    ```md
    # Manifest Reconciliation Report
    
    ## Cells Reconciled
    [Table: Cell | Manifest Updated? | Sections Changed]
    
    ## Algorithm Consistency
    [For each cell: manifest algorithm vs implementation — match or mismatch]
    
    ## Operational Flow Consistency
    [For each cell: manifest flow vs implementation — match or mismatch]
    
    ## Guarantees Verification
    [For each cell: manifest guarantees vs implementation — preserved or violated]
    
    ## Practices Consistency
    [For each cell: manifest practices vs implementation — match or mismatch]
    
    ## Semantic Consistency Summary
    [Overall: consistent or inconsistent. If inconsistent → STOP details]
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related