CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required step. Do NOT jump ahead to coding or implementation. The plan phase (step 1) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.

Anti-stall: this pipeline runs autonomously from step 1 through step 11 without stopping. After each subagent returns or each gate passes, immediately proceed to the next step — do NOT stop to report progress or wait for the user. A subagent completing is a signal to CONTINUE, never a signal to stop. The only valid stop conditions are: (a) a GATE says "stop the pipeline", (b) gh preflight fails, or (c) <promise>DONE</promise> has been emitted.

When invoking any skill referenced below, resolve its name against the available-skills list the host platform provides and use that exact entry. Some platforms list skills under a plugin namespace (e.g., tunan:plan); others list the bare name. Invoking a short-form guess that isn't in the list will fail — always match a listed entry verbatim before calling the Skill/Task tool.

Artifact model: one feature, one issue — the pipeline chains via comments on that issue, not separate issues or local files. A feature is a single GitHub issue for its whole lifetime. Its NUMBER #N — the feature issue — is the one handle threaded through every stage. The requirement is the issue body; each later stage lands as a marker comment on the same issue and adds a label. There are no separate tunan:plan or tunan:solution issues:

brainstorm produces the feature issue (body = requirement, label tunan:req)
plan consumes the feature issue and writes the plan as a comment on it (first line , label tunan:plan added)
work consumes the same feature issue, reading its plan comment
compound writes the solution as a comment on the same feature issue (first line , label tunan:solution added)

Every stage receives the same feature issue #N — never a freshly-minted plan or solution number. A stage's "done" is verified by checking the feature issue for its marker comment and label, not by listing a separate issue. There is no local-file fallback for these artifacts — never read or write a plan/req/solution as a local file.

GH PREFLIGHT (required — run before step 1; the pipeline depends on gh). Run these in order; if any fails, abort the pipeline and tell the user to fix the gh setup (install gh, run gh auth login, or set the repo). Do NOT fall back to local files:

lfg