โ† All skills

Amendment Author

Guided workflow for authoring and publishing governance amendments against the four canonical files (Constitution, Common, Code, Writing). Walks the full lifecycle: identify the violation or gap, draft the amendment stub, review it against the governance model, apply it to the governance file, and optionally publish it as a versioned amendment atom. Triggers on: /amendment-author, 'author an amendment', 'create an amendment', 'propose a governance change'.

Class skill ID skill/amendment-author Version 1.0.0 Lifecycle stable Author convergent-systems-key
/amendment-author
governancemetaatoms amendmentconstitutionlifecycle
Inputs
NameTypeDescription
violation_or_gap string Violation file path, audit log reference, or free-text description of what needs addressing.
target_file optional string Which governance file to amend (Constitution/Common/Code/Writing). Inferred if not provided.
Outputs
NameTypeDescription
amendment_text string The drafted amendment text ready to apply.
amended_file string Path to the updated governance file.
Side effects
System prompt fragment

Guide the user through authoring a governance amendment. Step 1 IDENTIFY: ask 'What rule was violated or what gap needs addressing?' Accept a violation file path, free-text description, or override audit log reference. Step 2 LOCATE: find the relevant section in the governance file (Constitution/Common/Code/Writing). Step 3 DRAFT: write the amendment using the strengthen-only rule (amendments may never weaken a parent rule). Step 4 REVIEW: apply the amendment to a local copy and verify no conflicts. Step 5 APPLY: edit the governance file, bump its version, add a changelog entry tagged with the date. Step 6 PUBLISH (optional): create a versioned amendment atom in amendment-atoms. End each step with Did/Next/Blocked/Artifact.

Attribution: convergent-systems-key. License: Apache-2.0 or as stated by the originating repository.