Finance Demo

Copilot + SDD Meeting Agent

A spec-driven development loop where one specification shapes prompts, code, validation and a follow-up email draft.

Runnable demo · Repo path: workshops/workshop3-copilot-demo

Structure Blueprint

Copilot + SDD Meeting Agent blueprint

Clickable pattern simulator

Interactive Browser Demo

This simulator does not replace the CLI run, but it makes each step, state, log, gate and final output visible in the browser.

Live pipeline

State inspector

Execution log

Current output

Step-by-step Design

01

Spec Context

The meeting-agent spec defines schema, quality rules, follow-up format, and validation constraints.

Spec as Contract
02

Copilot Plan

The implementation plan is generated from the spec, not from a vague one-shot prompt.

Plan-and-Execute
03

Prompt Chain

Extraction, validation, and follow-up email generation become separate controlled steps.

Prompt Chaining
04

Validation

The same spec checks required fields, owners, dates, length, and action-item completeness.

Generator-Critic
05

Skill Package

Prompt, schema, examples, and run path become a reusable work package.

Skill Package
06

Progressive Delivery

Move from mock path to model-backed path to team workflow only after checks are stable.

Progressive Commitment

Screenshots

Terminal run: SDD spec, minutes JSON, quality checks, follow-up email draft.
Terminal run: SDD spec, minutes JSON, quality checks, follow-up email draft.

Pattern Mapping

PatternDesign role
Prompt ChainingBreak one broad generation task into inspectable steps.
Plan-and-ExecuteUse the spec to shape implementation before generating code.
Generator-CriticValidation is a separate role with explicit quality criteria.
Skill PackageBundle prompt, schema, examples, and run path for reuse.
Progressive CommitmentPromote the workflow gradually as evidence accumulates.

Design Insights

Spec first changes the work

Copilot becomes more useful when it reads a contract rather than a wish.

Validation is not optional

For finance workflows, downstream actions have owners and deadlines, so checks must be explicit.

SDD connects design and delivery

The same document can guide development, runtime behavior, and audit review.

Run Path

cd workshops/workshop3-copilot-demo python3 -m venv .venv source .venv/bin/activate pip install -r requirements.txt cd src python main.py # optional visual walkthrough open ../visual/index.html
READMEworkshops/workshop3-copilot-demo/README.md
Blueprintimages/training/visual/workshop3-pattern-blueprint.png