Meetings · № 001
Jun 25, 2026 — kickoff: the AI Development sync
~34 min · Zoom · Chris, Shawn, John, Eddie, Brendan, JP, Maddy, Sam, Nick
Tools in play
-
Warp
Agentic, project-aware terminal, demoed by Brendan. Tabs per project, one-click commit, plain-English commands. Now subscription-based.
warp.dev ↗
-
GSD ("Get Shit Done")
Feed it project requirements; it plans and builds large features. Eddie & Maddy. Expect to test heavily. You get a strong first draft, not finished work.
opengsd.net ↗
- Claude Code & Codex The team's baseline. Agents run in the terminal, often several in parallel. Chris also runs Codex adversarially against Claude for review.
- Chrome DevTools MCP Eddie's pick for visual inspection and perf debugging. It found a subtle rendering bug in about an hour that could have taken a human a week. Install tip: "just tell Claude to install it."
- Ghostty · tmux · Zoxide Session management. Chris runs Ghostty tabs for parallel agents. Sam recommends tmux plus Zoxide (z <dir> to jump anywhere).
How people are working
Chris
Terminal-native, several agents in parallel. Built a personal project launcher (searchable repo homepage → opens a terminal with Claude pre-loaded). Exploring adversarial AI review and browser MCP. Tunes a global CLAUDE.md that forces terse output, and runs a nightly cron logging Claude insights.
John
VS Code + Claude. Pastes customer/support messages straight in → task list → execution, one long-running chat per project. Uses it for unit tests and sweeping the codebase for repeated bug patterns. Wants a standard set of review prompts for every project.
Brendan
Demoed Warp: project-aware agentic terminal, tabs per project, one-click commit, command auto-suggest, plain-English commands.
Eddie (most automated)
Claude Code in PHP Storm, max effort. "I don't code anymore." He plans, then throws it to GSD. Chrome DevTools MCP for testing/perf. Parallel project clones with separate DBs. Slash-command integrations (/Monday, /Asana, /explain). Production debugging via Vapor CLI + throwaway scripts. Email triage: Outlook checked 3×/day, Slack ping only for real email.
JP & Maddy
JP: near-identical workflow to John's, Codex and/or Claude, now full agent-driven. Maddy built the UTI app with GSD. Promising, but it needs heavy testing of what it gets wrong at first.
Sam (Blue Box)
Self-described "pretty anti-AI," and the source of the tmux/Zoxide recommendations. Blue Box is the main team not using AI yet. Follow up with Sam & Robert on where it could add value, starting with unit tests.
Business thread
Shawn: officialize how Creative2 bills for AI-assisted development. He wants a real, transparent model for clients rather than quiet use, and is open to a fun framing (treat the AI like an employee). Target: locked in by end of September, with a gradual client rollout.
Action items
- [ ]
Shawn — define and lock the AI-billing model (end of September, gradual rollout)
- [ ]
Team — document useful integrations & slash commands (/Monday, /Asana, /explain) so others can adopt them
- [ ]
John + team — standard review prompts for every project (docs, tests, security, performance, Composer audit)
- [ ]
Sam & Robert — where AI adds value on Blue Box; Chris to have Kyle share his DevOps AI workflow
- [ ]
Chris — shared team skills / global CLAUDE.md as a common starting point (this site is part of that)