ship-feature

Automating feature shipping requires coordinating briefs, CI checks, and PR workflows using Archon. This Skill transforms a feature brief into a merged PR by coordinating prep, launch, monitor, recover, review, merge, cleanup, and close phases. It enforces an Archon-based workflow with CI-gated checks and human verification steps to reduce cycle time and human error.

CI gating in an automated feature PR workflow monitors checks during the launch and monitor phases. The workflow enforces CI-gated checks, handles environment-skip scenarios, and requires human verification steps before proceeding to merge. This ensures the feature meets repository standards before the PR is merged and the worktree is cleaned up.

Shipping phased features end-to-end requires a configured Archon environment. The workflow relies on Archon to orchestrate the feature-development process, enforce conventions, and coordinate phases from prep to advance. Without an Archon environment configured, the Skill cannot transform the feature brief into a merged PR or automate the workflow.

Managing feature briefs for phased development involves placing them under docs/features/phase-<N>/ directories. The workflow applies to these phase feature briefs, encouraging reuse of existing module foundations and adherence to phase dependency order. This structured approach coordinates the feature from spec through to a merged PR and closes the associated issue.

The workflow handles environment-skip scenarios during CI monitoring, but it enforces CI-gated checks as part of the process. It requires human verification steps as described in conventions before merging. You cannot bypass the CI gates entirely, as they are integrated into the launch, monitor, and recover phases to ensure code quality before the PR is merged.