Feature delivery pipeline

This skill runs the other skills in order. Each phase ends at a checkpoint: a short summary in the user's language, the artifact path, the defaults you took and one clear question. Then wait. Do not start the next phase in the same message, unless unattended-run is active. The user often changes direction at a checkpoint; that is the point of it.

Conventions for the whole pipeline

Load these first and keep them active: simplified-technical-language, scratchpad-working-files, git-commit-organizer, no-slop-code, decision-record-log, traffic-light-findings, plain-visual-docs.

If the user asks you to run without them ("do not ask me", "take the decisions yourself"), also load unattended-run. It turns every checkpoint below into a logged decision and a status line, and it says which actions still need the user.

Phases

Invoke every phase skill with the skill tool, not by reading its file. If a project skill is not listed, read the project SKILL.md directly and tell the user. Do the same if the base directory that the tool prints is neither in this repository's skills folder (for example .claude/skills/ or .agents/skills/) nor the target of a symlink there. A user skill with the same name shadows it.