Maintain Release Story
Align accepted OpenSpec outcomes, project version conventions, distributable versions, dependency pins, and consumer-facing changelog prose without publishing.
Use when: Align accepted OpenSpec outcomes, project version conventions, distributable versions, and consumer-facing changelog prose when planning, preparing, or auditing a release without publishing it.
Install only this skill
Section titled “Install only this skill”arcantry skills link maintain-release-story --scope userThis links only maintain-release-story to the standard user location, ~/.agents/skills. Use --scope repo for one repository, or add --compat claude when that optional alias is needed.
Compatibility
Section titled “Compatibility”Source kinds: openspec, changelog.
What it helps with
Section titled “What it helps with”- Derive unit release impact and consumer-facing notes from schema-classified OpenSpec release artifacts.
- Verify release manifests, dependency pins, and native version sources across single, independent, or composed topologies.
History
Section titled “History”- 2026-08-25 - Model independent and composed release units: Projects can manage one release story, several independently versioned units or a composed product whose unit manifests pin exact direct dependencies, without turning child releases into implicit parent version changes.
- 2026-08-18 - Coordinate project knowledge and agent workflows with Arcantry: Arcantry provides local-first project configuration, safe repository adoption, a portable catalog of focused agent skills, and one documented workflow for maintaining project intent, release meaning, task intake, verification, and audience-safe content.
Examples
Section titled “Examples”Prepare a product release
Section titled “Prepare a product release”Prompt
Use the maintain-release-story skill to prepare the next release unit from completed OpenSpec changes without publishing it.
Expected outcome
A verified release set aligns the configured version strategy, manifests, dependency pins, components, and consumer-facing changelog entries.
Audit release consistency
Section titled “Audit release consistency”Prompt
Use the maintain-release-story skill to check whether unit versions, dependency pins, and release notes match the accepted product changes.
Expected outcome
Version, dependency, ownership, or release-story drift is reported with its authoritative source and exact repair boundary.