Show Me

For engineers who already ship with agent runtimes and need to see what lands on disk before reading harness terminology.

After this page you can name each delivery artifact and choose between macro (/sdlc:goal) and micro (/implement-feature) entry points.

---

Example input

Build a SaaS onboarding flow with email verification.

Same class of intent as a product brief in Plane or a paragraph in chat — not a single-file patch.

---

What happens

Step	System action	You receive
1	Mode classification	greenfield / feature / fix / content
2	Decomposition	vertical slices in a run plan
3	Plane hierarchy	epic + child tickets with specs
4	Worktrees	feat/JAMBU-N-* branch per ticket
5	Per ticket	spec → implement → review → QA gates
6	Integration	merge wave PRs, joint E2E
7	Deploy	CI deploy URL on manifest
8	Handoff	.sdlc/handoffs/LATEST.md for the next session

Macro path command:

/sdlc:goal Build SaaS onboarding with email verification

/sdlc:e2e is deprecated; use /sdlc:goal (ADR-020). Manual step-through: /sdlc:goal --manual.

Micro path (one slice only):

/implement-feature JAMBU-42

---

Artifacts produced

Counts below come from the reference docs-site engineering run (docs-site-engineering-20260526) — a real multi-wave delivery, not a toy demo.

Artifact	Typical scale
Plane tickets	1 epic + 9 child issues (JAMBU-87–95)
Git worktrees	1 isolated tree per ticket
Pull requests	1 PR per slice, merged in waves
Engineering pages	Starlight content + flow diagrams under app/public/images/docs/
QA / visual evidence	manifests under .sdlc/evidence/{run_id}/
Run manifest	.sdlc/workflow-runs/{run_id}/manifest.yaml
Deployment record	CI run URL + production smoke gate
Session handoff	timestamped file in .sdlc/handoffs/

Production constraints: stage transitions do not advance on model claims. Gates read filesystem paths and API state. Deploy nodes require a recorded CI URL. Post-deploy smoke is a separate gate from merge.

---

Without vs with

Without AI Native SDLC

Feature request in chat
  ↓
Agent writes code on main
  ↓
QA skipped or ad-hoc
  ↓
Plane / Jira stale
  ↓
No deploy evidence
  ↓
Next session: cold start, lost intent

With AI Native SDLC

Intent
  ↓
Spec + ticket hierarchy
  ↓
Worktree per ticket
  ↓
QA evidence + gate PASS
  ↓
PRs + CI deploy record
  ↓
Handoff + trace for next agent

The home splash shows the same chain in one screen: site home.

---

Worked chain (component names)

Architects who need file-level names: Architecture documents the worked /sdlc:e2e chain (trigger → manifest → waves → evidence) for run docs-artistry-20260530.

---

Read next

Question	Page
Should I install this on my repo tomorrow?	Introduction
Install and three-layer map	How It Works
Internal architecture name (PCRA) and C4	Architecture