AI TO GROW: MEETING TO PROTOTYPE Workshop resources, 18 October 2026 Use the complete starter ZIP and start at step 2. Step 1 is optional and uses the live-build ZIP. Open the same extracted project folder in both tools. You start each stage manually. Review the spec before supplying approval. Full instructions and fictional clarification answers: https://aisandboxlab.com/ai-to-grow-notes#takeaway-pack 1. Create the first skill (optional) Create a project skill named meeting-to-spec for this workshop. This is a draft for a three-minute live exercise. Create the files directly; we will inspect and test the draft in the next step of the demonstration. Its input is a meeting transcript and the task we want to explore. It extracts final decisions, constraints and gaps with source references, asks the human questions that change the prototype, and waits for answers. It then writes a short spec using handouts/working_brief_template.md. Keep facts, human answers and assumptions distinct. Preserve English. The spec needs a version, one user journey, exclusions and observable checks. Stop for a human's Proceed, Revise or Pause on that version before any build. Do not invent answers or approval, and do not build the prototype in this skill. Create the skill in .agents/skills/meeting-to-spec for Codex and expose the same instructions in .claude/skills/meeting-to-spec for Claude Code. Put a copy of the template inside the skill so it can be reused elsewhere. 2. Claude Code prepares the brief Read .claude/skills/meeting-to-spec/SKILL.md and use that skill on inputs/meeting_transcript.md. The task is to let a delivery recipient choose another available delivery slot without calling support. Work in English. Save outputs in outputs/. Ask the material clarification questions and wait. Keep the transcript unchanged. Do not build or invent human approval. 3. Human Check and build handoff Proceed with spec [actual version] for this local fictional prototype, including these reviewed assumptions: [list or refer to their IDs]. Record this decision and its version faithfully. Create outputs/build_handoff.md for Codex. Include the original task, paths to the source, clarifications and approved spec, the exact approved version and decision, acceptance check IDs, exclusions and unresolved questions. Do not invent reviewer details or approval. Do not build. The next step will run separately in Codex. 4. Codex builds Read .agents/skills/spec-to-prototype/SKILL.md and use that skill. Read outputs/build_handoff.md, the complete referenced spec, source and clarifications. Verify that the human Proceed applies to this version and scope. If absent, stale or contradictory, stop and identify the missing decision. Build outputs/prototype/index.html as one offline HTML file with sample data. Use a polished, readable layout on laptop and phone; keep the approved scope. Run available browser checks and save actions, observations, failures and untested checks in outputs/build_notes.md. Do not infer passes from code alone. Create outputs/verification_handoff.md with the exact spec version, prototype path, how to open it, evidence paths and limitations. Do not approve your own outcome, contact anyone or publish. Return the local preview. 5. Fresh Claude Code verifies Read .claude/skills/validate-outcome/SKILL.md and use that skill. Read outputs/verification_handoff.md, the original transcript and task, outputs/spec.md and outputs/clarifications.md. Inspect the prototype and recorded evidence yourself; do not adopt the builder's verdict. If browser tools are available, exercise the checks and record new observations. If not, identify which supplied evidence supports each finding and leave unsupported checks Not tested. Label agent-operated checks separately from intended-user observations. Here are the actual volunteer observations: [paste observations, or state that no volunteer has tested it]. Save outputs/validation.md with Pass, Fail or Not tested for every check, the main mismatch or evidence gap, and the smallest next action. Do not edit the prototype, change requirements, invent approval or publish.