One Team, One Repo, One-Day Sprints

▶ Watch (02:42)

For 12 months, PALO IT’s developers have not written a single line of code. They manage context, write prompts, and define rules. The AI generates the rest. That shift came from a real bottleneck: uplifting only the developers just made them wait faster for designers and product managers.

The fix was a unified repository where designers, developers, and AI agents work from the same files. Design artifacts, user stories, and code live in one place, versioned the same way. Singapore Airlines’ meal selection platform shipped in half the expected time, with 95% of code and documentation generated.

Design Without Leaving VS Code

▶ Watch (07:15)

The VS Code design demo (07:15) replaces external design tools with a single VS Code extension. Designers pick colors, typography, and motion effects in a visual UI. The backing store is JSON, so Copilot reads it directly to build components. From the same chat, the team generates user personas, user journeys with emotional scores, and WCAG accessibility reviews, all versioned in the repo like any other commit.

Context Graphs and Cascade Changes

▶ Watch (12:02)

A larger repo makes context harder to fill per prompt. PALO IT’s context graph demo (12:02) shows the fix. A YAML file describes the entire repo, with summaries, relationships, and source files per component. A VS Code extension surfaces it as a queryable UI, selecting the relevant graph nodes before handing context to Copilot.

The repel operation handles cascade changes. Change one user story and repel propagates it to APIs, database schemas, and tests automatically. In autonomous mode it creates a GitHub Issue, assigns it to Copilot Coding Agent, and opens a PR. No developer input required.

Notable Quotes

they haven’t been writing any line of code, which is pretty good. Dimitri Baikrich · ▶ 2:45

It’s not vibe. It’s not. Dimitri Baikrich · ▶ 3:10

It’s really to focus on the engine which is generating the code. Dimitri Baikrich · ▶ 6:15

Key Takeaways

  • PALO IT developers have not written code in 12 months, working on context, prompts, and system rules instead.
  • A unified repository makes design artifacts, user stories, and code visible to both designers and AI agents in one place.
  • The repel operation propagates a single change across APIs, databases, and tests automatically via Copilot Coding Agent.