Using Nautelle
Stacks
Staged cards that share one design.
A stack is a group of cards in ordered stages, usually under one shared design. Use it when one piece of work has parts that happen in order and must look alike, such as the shared layout first and the per-screen cards after. Stacks are numbered S-<n> per project.
How a stack is made
- By the intake. The planner proposes a stack when you describe one larger piece of work, or several UI changes to one surface. Accept it from Drafts. A UI stack starts with a Foundations stage before the features.
- By hand. Select two or more cards that are in no stack and not in Inbox, and group them. They go into one stage with no dependencies between them. A card can join or leave later.
Stages
Cards of one stage can run in parallel. Every card of stage N+1 depends on every card of stage N, written as ordinary dependencies. That is why Ready, Waiting and Auto-run work for stacks without special handling. There are no nested stacks.
One shared design
With the design switch on, the stack has one design, drawn for the whole result and approved once. Until it is approved, Run is disabled on every card of the stack with the reason shown. A card that needs its own design keeps it, and its design turn reads the stack's approved design as a reference. Round 1 of each card commits the approved frames into its branch and names them in the worker prompt. Switch the design off on the stack page and nothing is held. See Design.
On the Board
A stack is one face in the column of its least advanced unfinished card, with accepted over total progress and the current stage. Expand it to see its cards by stage. Opening it goes to the stack page, which holds the design, the stages and the generate and approve controls, and works on a phone.