Delicious

Stage contracts

Each stage reads the App Spec (plus the relevant prior outputs and skills) and writes back to it or produces an artifact the next stage consumes. The conceptual tour is in The 10 stages; this is the I/O reference. Three stages pause for a human tasting.

01 · Discovery

  • In: the idea; the operator config.
  • Out: pain-brief.md — the real problem, the audience, and the bar for "what good does."

02 · Spec (Idea + Brand tastings)

  • In: interview.yaml, the answers, the pain brief, the operator config, the App Spec schema; the Onboarding, Monetization, and AI skills.
  • Out: app.appspec.yaml with product (and the seed of brand) filled. The producer runs the interview and enforces the gates.

03 · Branding (Brand tasting)

  • In: the App Spec product; the Brand, Copy, and Design skills.
  • Out: the App Spec brand section — name, bundle_id, accent_hex, the 1024px icon, appstore_name, subtitle.

04 · Scaffold

  • In: the brand‑locked App Spec; the Project.swift + adapter templates; the integrations map; the operator config; the Architecture (+ AI) skills.
  • Out: Project.swift, a .gitignore, a Sources/ skeleton wired through DeliciousKit + the chosen adapters, and the App Spec architecture section filled (status: building).

05 · Codegen

  • In: the scaffolded App Spec + project; the pain brief; the Deliciousness Standard; the Design, Architecture, Onboarding, Copy, Monetization (+ AI) skills.
  • Out: Sources/** — the screens and logic — plus a screenshot per screen. Loops with Dogfood until it builds clean and answers every cited pain.

06 · Integrations

  • In: the App Spec integrations; the integrations map + adapter templates; your .env; the Onboarding, Monetization (+ AI) skills.
  • Out: the integration adapter Swift files and a filled .env. You only supply keys; this stage does the plumbing and the ATT priming.

07 · QA (the Deliciousness Gate)

  • In: the App Spec + Sources + pain brief + operator config; the Deliciousness Standard; the Design + Compliance skills; qa_gate.py.
  • Out: scores.json (the tenet scores), deliciousness-scorecard.md, preflight-report.md, test results, and screenshots. The gate must pass (every tenet ≥ 2, total ≥ 7/9, zero HIG violations, clean pre‑flight) or it loops back to Codegen.

08 · Dogfood

  • In: the built app; the pain brief.
  • Out: a value‑and‑feeling critique — does it actually solve the problem, and does it delight? Loops back to Codegen when it doesn't.

09 · ASO

  • In: the App Spec + the QA screenshots; the Copy skill.
  • Out: the App Spec aso section (keywords, description, promo), framed screenshots, and the store metadata.

10 · Release (Final tasting)

  • In: the App Spec + the signed build; the operator config (Apple identity + review contact); the Compliance skill.
  • Out: the app submitted to App Review, with the pre‑flight passed and content rights declared — after you tap submit.