Who this is for and how to read it
For product managers, business analysts, project and team leads who do not code. If you already know the difference between a chat and an agent, skip to Part 3.
Words used in these notes, in plain language
| Word | What it means | Everyday comparison |
|---|---|---|
| Agent | An AI that does the work on your files and tools, not only answers questions | A colleague who opens the files and does the task |
| Skill | A reusable set of written instructions for one kind of task | The picture steps in flat-pack furniture |
| Context | Everything the agent knows about the task: your files, rules and question | The briefing you give before work starts |
| Context window | How much the agent can keep in mind at one time | The size of a desk: it fills up |
| Connector | A link that lets the agent reach Jira, Drive, Figma and similar tools | A plug into another system |
| Sub-agent | A helper with its own context for one small job | An assistant with their own desk |
| Handoff file | A saved note that tells the next session or tool where things stand | A note left for the next shift |
| Spec | A short document that says what to build and how you will check it | A brief with a checklist |
| Prototype | A clickable draft, not real software | A mock-up you can walk through |
| CLAUDE.md, AGENTS.md | The rules file a tool reads first in your project folder | The house rules on the door |
Part 1. Chat versus agent
In plain words: a chat is a conversation. An agent is a colleague who can open your files, do the task and show you the result to check.
- In a chat you talk. An agent does the work: it reads your files, runs tools, checks its step and saves results.
- Correction from the session: chat products today also have connectors, skills and file creation (Anthropic, 16 September 2026). The practical difference is local file and tool access plus a loop where the agent acts and checks, with you steering less step by step.
- An agent is more than a model. It has context (the files and instructions you give it), skills (reusable instructions), memory, tools (build a doc, build an HTML page, analyse a CSV) and connectors (Jira, Confluence, Google Drive, Miro, Figma, repositories).
- Examples of agent tools named in the session: Claude Code, Codex, Google Antigravity. Andrew mostly works in VS Code with the Claude Code and Codex extensions.
Part 2. The workflow shown
In plain words: we gave the AI a messy meeting record, answered its questions, and got a clickable draft of a new feature. Then we checked the draft against what we had agreed.
The input was a meeting transcript about one problem: a delivery recipient cannot be home, and wants to reschedule so the courier does not come in vain.
- Raw transcript is the starting point. Work conversations are the foundation for tangible output.
- A skill called meeting-to-spec turns it into a lightweight spec. The skill contains a spec template and a description of how to do the job.
- The agent asks clarifying questions. Better answers give a better result. Answers were given in English.
- Human review of the spec. Andrew noted it will not match your own template unless you give the agent your template.
- Handoff: Claude wrote a handoff file for Codex, which then built the prototype with a spec-to-prototype skill. The agent first proposed a screen plan and asked whether to proceed.
- The result was a clickable HTML prototype with no backend: an SMS arrives, the user picks another delivery slot and confirms.
- Verification: Codex wrote a verification handoff, and Claude was asked to validate the outcome against the spec with a validate-outcome skill.
What did not work: the validation step failed in the session ("something went wrong", attributed to setup or timing). Andrew pointed participants to the prompts on his site to run it themselves. The prototype also showed a map that was not needed, and the second run looked different from the first.
Part 3. Key ideas
In plain words: write instructions once, reuse them, and always look at the result before it leaves your desk.
Skills are reusable instruction packages. Andrew's analogy: the assembly instructions that come with IKEA furniture. The parts are your files and tools, the instruction sheet is the skill, and the finished piece is your spec, report or prototype. A good skill has a clear name and clear steps. Technically it is a folder with a SKILL.md file; the agent reads the name and description first and loads the rest only when the task matches (Codex docs). The same format works in Claude Code and Codex.
Do not hand-write skills; write them with AI and then edit. Claude and Codex have a built-in skill creator. Speak your intent (Andrew uses voice dictation with Wispr Flow), then read and edit the markdown file. With many skills, consider a skill for reviewing and verifying skills.
Skills from outside need a security check. Skills can contain executable code. Anthropic's own guidance is to install only from trusted sources and to audit anything else by reading every bundled file (Anthropic). Correction from the session: asking the agent to review a skill helps, but it is not enough, because a few lines of plain instructions can also be harmful. A person reads it too. One study reported by a news site found about a quarter of 31,132 public skills had at least one vulnerability (AI Weekly); the figure has not been independently verified.
Be specific about output. "Summarise this" gives vague results. Ask for a fixed number of bullets, and for proof of each statement from the source.
Outputs vary. Models are probabilistic, so the same input can give a different result, even at temperature 0 (paper). Work shifts from producing to checking, like reviewing a junior colleague. Andrew noted that some people feel only slightly more productive: they can do more but must verify more. One study of experienced developers found them 19% slower with AI tools while they believed they were faster (summary); that was a different group from PMs and BAs, so treat it as a caution, not a rule.
Always verify. Checking with the same model is the weakest option, because models tend to favour their own output (paper). Prefer a different model, then tests or a checklist, then the person who owns the task. Do this especially for anything going to clients, engineers or leadership. Andrew's own example: a day earlier a wrong QR code was generated by Codex because the agents.md file was not set up the way Claude's setup was. "Never trust AI."
Retro with the model. After a bad output, ask the model to update CLAUDE.md, agents.md or the skill so it does not repeat the mistake.
Give design guidance. Without a design system or examples, output looks generic. If your team has a design system, connect Figma and reuse the tokens. On a ten-year-old project the design system may itself be out of date; ask the designer for the latest.
Handoff files are useful when a context window runs out or when switching tools or agents: the next session reuses the artifact instead of losing it in the conversation.
Part 4. Choosing tools and models
In plain words: use a stronger model to plan and a faster one to build, and keep notes in files so nothing is lost when a chat ends.
- Andrew's personal setup: a $20 Claude plan for planning and documentation, a $100 plan for Codex for building from a good spec, a Gemini plan at about $20 a month for deep research (Google AI Pro is listed at $19.99). Correction: the $100 option is a ChatGPT Pro plan that includes Codex (TechCrunch), and Claude Max 5x is also $100, so price tiers match and what differs is usage limits, which change often. Check current plans.
- Mental model: a stronger model is a senior architect who plans; a cheaper model is a mid-level engineer who builds to the plan; sub-agents are for research and keep your main context clean. This matches Claude Code's opusplan option (docs) and how sub-agents work (Anthropic).
- Voice dictation: Andrew dictates prompts and edits with Wispr Flow on its paid plan. Flow has a free plan; Flow Pro is $15 a month, or $12 a month billed yearly (Wispr pricing).
- Choice is partly taste. Some artifacts he likes better from Claude.
- Advice for beginners: start with anything, do not overthink the model. If you have a work subscription, use what your engineers use.
- Spec frameworks: Andrew uses OpenSpec at work and Superpowers for private projects; tried BMAD and found it did not fit. Stick to what your team uses.
- A tool to try: OpenChamber, an open-source desktop, web, mobile and VS Code interface built around OpenCode, with a session context panel. Andrew uses it to work with several models in one place. Its site does not mention Codex, so check which providers you can connect.
- Claude Cowork versus Claude Code: Andrew reported that Cowork does not show context or token limits, compressed a long chat without warning and lost artifacts. Another attendee lost Cowork sessions after reinstalling the desktop app. Similar user reports exist (issue tracker); these are user reports, not vendor statements, and the product may have changed. Both tools read the same CLAUDE.md in a shared folder (guide). Anthropic's merge announcement says nothing about context or token visibility, so those points remain user reports. Lesson: keep outputs and handoffs as files in your project folder, not in chat history.
- Update: as mentioned in the room, Anthropic's announcement of 16 September 2026 merges Cowork and chat into one conversation, and Claude Design now also works inside conversations. Claude Code remains a separate tool (announcement, help article). It is rolling out first to Pro and Max plans. The prototype-to-code handoff mentioned in the room is Claude Design sending a bundle to Claude Code (tutorial).
- Working from a phone: Claude Code has Remote Control to continue a local session from your phone (Help Net Security). Andrew chooses not to use it, to keep a break from the computer.
- Instruction files: Codex reads AGENTS.md and Claude Code reads CLAUDE.md (guide), which explains the QR bug. Keep one shared set of rules or link them.
Part 5. Adoption in teams
In plain words: try it on one small task with a few people, and measure the time saved before you roll it out wider.
- Share practices, not just personal tricks. If a team used to write Jira stories in a format, create a skill for that format and share it.
- Andrew's observation: where managers use AI coding assistants themselves, their teams adopt faster, because they lead by example.
- Andrew's observation: some teams already have a product manager plus a tech lead shipping features, and he expects this to become common in a year or two. Quality assurance for fully AI-built work was described as an open problem: it needs the engineering lead (tests, evals, tools such as Playwright were mentioned by an attendee).
- Benefit shown for non-coders: prototype yourself, validate with customers, then bring a spec and prototype to engineering rather than wait two to three months for capacity.
- ROI: Andrew's position is that a full ROI study is a large consulting project. A small before/after pilot on one task (time and rework) is far cheaper, and practitioner guidance recommends measuring cycle time, rework and whether use spreads beyond early enthusiasts (guide).
- Learning to use these tools: Andrew's experience is one and a half to two and a half weeks to start using them at work. He has trained more than 70 non-coders.
Updated since the session
Part 6. Appendix: questions from the room
| Question | Answer given |
|---|---|
| Did you create the skill yourself? | With AI help, then edited and reviewed. Use the built-in skill creator. |
| Where can we download skills safely? | Prefer trusted sources such as the tool vendor's own repositories, and read the whole skill yourself before installing. An AI review alone is not enough (see Part 3). |
| Why not one Codex subscription instead of Claude plus Codex? | Cost and taste. Andrew likes Claude's output for some artifacts. See Part 4 for how the plans compare. |
| Which spec frameworks have you tried? | See Part 4. Depends on what the team uses. |
| Same data, different prototype? | Yes. Outputs vary; guide with samples and a design system. |
| Do you use Claude Cowork for prototypes? | Not much; goes straight to Claude Code. Uses Cowork for office documents. |
| Can you work from a phone? | Andrew deliberately does not. Others use scheduled tasks in Cowork or voice notes to a chat assistant. Remote Control for Claude Code exists. |