This is not about a better prompt. It is about better context, clearer structure, and a shared language between analysts and engineering.
- Length: 1 day (8 hours)
- Price: from 18 000 CZK / participant (ex-VAT), quoted per group
- Format: on-site, custom-built for your team, on demand
- Max participants: 15
- Who it's for: business analysts, product owners, product managers, and people who prepare work for engineering
- Prerequisites: real requirements, templates, or backlog examples help, but are not required
- A specification template analysts and developers can both work with.
- Prompt templates for turning emails, notes, and tickets into useful requirements.
- A way to validate system reality with AI using documentation, repository context, or technical notes.
- A list of missing context analysts should resolve before work moves to development.
- Simple governance rules for what belongs in AI tools and what does not.
Morning: request, context, and structure
Block 1: From messy input to a first specification
- We work with real requests, sticky notes, emails, or meeting notes.
- AI helps structure information. It does not replace analytical judgment.
- We show where AI hides ambiguity and how the analyst brings it back into view.
Block 2: Context-first work
- What an agent needs to know: glossary, domain rules, past decisions, architecture, and system links.
- How to turn that into a shared team context library.
- When a chat is enough, and when Claude Code in VS Code with controlled repository access makes sense.
Afternoon: your own use case and adoption
Block 3: Specification for developers
- Participants take one real request and prepare a first version of the specification.
- AI helps find gaps, edge cases, affected systems, and contradictions.
- We compare the output with what developers need for estimation and implementation.
Block 4: How to adopt it in the team
- Shared output template.
- Repeatable prompts for common analyst tasks.
- Agreement with engineering on how to assess specification quality.
- First-month plan: one request, one template, one measurement of follow-up questions.