The goal is not to prove that AI can write code. The goal is to set up a workflow that speeds the team up without lowering quality.
- Length: 2 days (2 × 8 hours)
- Price: from 18 000 CZK / participant / day (ex-VAT)
- Format: on-site, adapted to your stack, on demand
- Max participants: 15
- Who it's for: developers, QA, DevOps, tech leads, and architects
- Prerequisites: repository-based work, development experience, and access to approved AI tools
- An AI-supported development workflow covering planning, implementation, tests, review, and debugging.
- Team rules for Claude Code and Cursor, versioned in the repository.
- A first set of commands or skills for repeated tasks.
- An AI code review approach that complements human review.
- A decision on where MCP helps and where local context is safer.
Day 1: tools, context, and planning
- Set up Claude Code, Cursor, and whole-workspace context.
- Context files, project rules, prompt templates, and shared team configuration.
- Spec-driven work: plan first, then small verifiable steps.
- Tests as context for implementation.
Day 2: implementation, review, and team usage
- Iterative implementation on prepared or team-specific work.
- AI code review and checks against Definition of Done.
- Debugging from logs, error messages, and tests.
- MCP as controlled access to internal systems and documentation.
- Final team playbook: what to use tomorrow, what to adopt later, and what to avoid for now.