openspec-ship

To generate as-built documentation for shipped features, use the openspec-ship Skill during the SHIP phase after verification passes. It automates OpenSpec documentation generation and archiving to preserve the completed code artifacts.

OpenSpec documentation generation prefers the OpenSpec CLI for reliable operations, but does not strictly require it. The Skill provides Claude-native template fallbacks to generate as-built documentation if the CLI is unavailable.

Feature archiving during the SHIP phase works by automatically invoking the documentation generator after code verification passes. It preserves as-built OpenSpec artifacts alongside Superpowers execution artifacts to maintain a historical development record.

You should skip OpenSpec documentation generation when specific predefined skip criteria are met during the SHIP phase. The Skill evaluates these conditions automatically to avoid compromising the integrity of the feature development process.

The best way to preserve as-built artifacts from feature development is to automate OpenSpec documentation generation during the SHIP phase. This ensures permanent historical records are created alongside Superpowers execution artifacts.

OpenSpec documentation fails to archive shipped features if the OpenSpec CLI is missing or unavailable, or if the SHIP phase verification has not successfully passed. It may also fail if required execution artifacts are incomplete.