work

To execute a development plan step-by-step, the Skill breaks plan files into actionable tasks and tracks progress by marking items as in progress or completed. It maintains task state by updating plan checkboxes as each code change is implemented.

Managing feature branches and preparing conventional commits is handled by validating the current branch state, creating a feature branch, and generating commit messages and PRs. This enforces incremental commits alongside completed task items.

Yes, you can enforce testing and linting before shipping code changes. The Skill requires tests to pass and runs linters to verify quality, ensuring all plan checkboxes are checked before preparing commits and PRs for feature development or bug fixes.

The best way to turn written development plans into a repeatable workflow for bug fixes is to follow a plan file step-by-step. The Skill validates branch state, creates a feature branch, runs tests, and updates plan checkboxes until the task-driven sprint is complete.

You need a plan file or a recent plan to use this task-management workflow for shipping features. The Skill executes the specified plan file by breaking it into tasks, running tests and linters, and preparing commits and PRs until all checkboxes are complete.

Plan execution stops before shipping if tests fail or checkboxes remain unchecked because the workflow enforces quality by requiring tests and linters to pass. It verifies all plan checkboxes are completed before preparing commits and PRs to ensure reliable feature delivery.