implement-ship

You can automate the git workflow from commit to pull request merge by orchestrating code development, PR creation, CI monitoring, and merging within a single session. This requires state tracking via a .workflow-state.json file.

The best way to implement and ship a feature phase without manual intervention is to use an integrated workflow that combines code development and shipping functionalities. It automatically commits code, creates a pull request, and monitors CI status for merging.

Yes, you need a .workflow-state.json file to track state for automated CI/CD workflows. This file enables the system to orchestrate the implementation and shipping phases seamlessly across your structured feature development process.

Yes, you can monitor CI status and automatically merge a pull request after building a feature. The workflow handles pull request creation, tracks continuous integration checks, and completes the merge once validation passes.

The implement-ship skill handles structured feature development workflows by delegating to separate implement and ship skills. It orchestrates these phases using a defined plan document and state tracking to build, review, and merge code automatically.

You should not use a single-session build and merge approach if your feature requires multi-phase planning outside the current session or lacks a defined plan document. The workflow relies on structured phase definitions and state tracking to function correctly.