Continuous Dev Cycle

Use this skill to make a repo's development loop explicit and repeatable: idea capture, sprint planning, implementation, validation, PR or review, merge, release prep, publish, and release notes.

Planning-First Gate

Start in a planning-first posture for workflow setup or substantial workflow changes. Inspect the repo, ask release-profile questions that cannot be answered locally, propose the workflow, and wait for explicit user direction before mutating files. If the current environment has a formal Plan Mode, use it. If not, still behave planning-first in chat.

Ask only questions that affect the workflow design. Cover these choices when they are not discoverable:

• Project visibility: public, private, internal, local-only, or mixed.
• Delivery type: GitHub artifact release, package registry, deployed app/SaaS, platform changelog, blog or social announcement, PR merge only, or custom.
• Release audience: developers, admins/operators, end users, internal team, customers, or mixed.
• Version source: manifest, version file, deployment version, calendar/date release, changelog-only, or none yet.
• Exit artifact: tag, GitHub Release, package publish, deployment, external changelog post, PR merge, or a combination.

First Pass