From Michael Holley's Dev Workflows
Execute a unit of work end-to-end: plan, implement with tests, validate, then commit. Use when user wants to ship work, build a feature, fix a bug, or implement a phase from a plan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflows:ship-itThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Take a unit of work from intent to committed change: plan, build, validate, commit.
Take a unit of work from intent to committed change: plan, build, validate, commit.
Read any referenced plan, issue, or PRD. Explore the codebase for the relevant files, patterns, and conventions. If the task is ambiguous, ask the user to clarify scope before proceeding — don't guess past a user-owned decision.
If the task isn't already planned, create a short plan: ordered steps, files touched, tests to add. Present it briefly, then proceed.
Build the plan, matching the surrounding code's style.
Add or update tests covering the new behavior and its edge cases. If the repo has no test setup, propose the minimal one rather than skipping tests silently.
Detect and run the project's validation scripts; fix failures and re-run until green. Never claim green without running them.
scripts when present — typecheck, lint, test, build.Once validation passes, show the diff summary and proposed message, and confirm before committing. Branch first if on main. Don't push or open a PR unless asked.
npx claudepluginhub michaelholley/cc-plugins --plugin dev-workflowsCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.