Blue-sky feature pipeline

A feature moves through eight stages after a one-time setup, each owned by one kind of session whose authority ends at a checkable point. The boundary is the point: no session holds the whole feature, so a session can be compacted, closed, or replaced between stages and the next one starts from what was written down. What is written down lives in the issue tracker and the repository — the brief's changelog, a beat's issues and labels, a ticket's PR — never only in a session.

Every stage names the skill that does its work and the fallback without it; the pipeline points at skills and requires none. The skill names in this file are roles first; where a specific skill is named, it is an example of the role. A person working the stages by hand reads WORKFLOW.md, which carries the same stages as a checklist with the reason for each.

Session map

#	Stage	Session	Starts from	Produces	Hands off via
0	Setup	once per repository	a repository	skills, templates, workflows, labels, branch protection	—
1	Operating picture	once, refreshed on drift	the set-up repository	vocabulary and the guidance scaffold	the repository
2	Brief	one session	a feature idea	a design brief with a changelog	the brief
3	Prototype	one session drafts; the human runs the tool	the brief	a prompt set; pinned outputs	the pinned folder
4	Reconcile	one short session — a gate	pinned outputs and the brief	a dated changelog entry; go or no-go	the brief
5	Beats	one session, expecting compaction	the amended brief and the pinned prototype	the port; one stub issue per beat; a handoff document	the stubs
6	Spec	one session per beat, resumable from its issues	one stub and at most a handoff	a spec; its tickets	the tickets
7	Ticket	one session per ticket, own branch and worktree	one ticket	a reviewed, green, open PR	the PR
8	Land	any session acting for the beat	a reviewed, green PR	the merge; the ticket closed; the beat closed on its last ticket	—

bluesky-feature-pipeline

Blue-sky feature pipeline

Session map