AI-assisted projects rarely fail because of the model. They fail because of missing specifications, unreviewed results, and configuration management that nobody can trace anymore. That's your home turf as an assessor – just approached from the other direction: you know the process. In this training, you run it yourself.
No slide deck – more than a certificate of attendance: a repository you'll keep using afterward.
Every day ends with a tangible state in your repository. You build with an agent team of your own: architecture, requirements, development, testing, and quality assurance.
What models can and cannot do, tried out in conversation. You tell the model who you are, and together you find errors in your own field. In the afternoon, you sharpen your project goals and get your first architecture proposal by prompt.
Roles, documents, and how an AI agent team works together – and where the limits of delegation lie. You make one task delegable, set up your project team technically, and start your first development run with your own toolchain, API keys, and repository.
Initializing roles and consciously handing over decisions – but also defining what you won't hand over. You set your own permission rules for data security, distinguish stakeholder requirements from software requirements, and write your first requirements with criteria.
Making it repeatable with CLAUDE.md, skills, and hooks – trust, but verify. Tests as gates, reading an agent's changes, independent review. In the afternoon, you run two release cycles in your own project.
The final day belongs to your projects. First we check together whether the expectations you brought on day 1 were met. Then everyone presents their own tool in 30 minutes – goal, agent team, live demo, evidence and what you learned. In the afternoon you put your assessor's hat on: which evidence do you ask for when agents wrote the code, and where does judgement stay with people? We close with the final survey and what we as trainers take away from the week.
To take with you: The full agenda as a PDF – 20 pages: learning objectives, the weekly format, detailed daily schedules, prerequisites, costs, dates and price, and terms of participation.
Download PDF (354 KB)Budget for €50–80 in incidental costs of your own. All accounts are set up in your name and remain in your hands.
Two cohorts to choose from. In each, the five training days are spread over two weeks – with at least one free day between sessions to keep working on your own project. Pick the date that works for you.
This first delivery is aimed mainly at friends, acquaintances, and long-time colleagues – which is why, alongside the discounts, there's also the option to pay with time instead of money.
Time for time instead of an invoice: you take part in the full five days and, in return, contribute two and a half days of effort to a SPICEy3 project. What exactly, we'll work out together beforehand – it should match what you're already good at.
Request a QuoteSPICEy3 Consulting GmbH – training "Professional Tool Development with Claude Code"
This English version is a courtesy translation. In case of doubt, the German version prevails.
These terms apply to registration for and participation in the training "Professional Tool Development with Claude Code" by SPICEy3 Consulting GmbH (i.G.), Wiesenweg 3, 26434 Wangerland ("SPICEy3"). They apply to entrepreneurs within the meaning of section 14 of the German Civil Code (BGB) who book the training in the course of their professional or commercial activity.
Registration is made by e-mail to kosmas.kopmeier@spicey3.de. The contract is concluded upon written confirmation by SPICEy3. The number of participants is limited to a maximum of eight per cohort; if a cohort is overbooked, the order in which registrations were received decides.
SPICEy3 provides the services described in the current schedule: five training days online, continuous support for the participant's own chosen project, practice repositories and templates for further use, and office hours as needed. Changes to the schedule that do not materially impair the purpose of the training remain reserved. After the training, participants receive a certificate of attendance. It confirms attendance and summarizes the learning content of the individual training modules. It does not certify learning outcomes and is not a personal certification.
Participants are responsible for meeting the technical and organizational prerequisites (see the prerequisites page: own laptop, administrator rights, Claude Pro account, GitHub account, stable internet connection). If these prerequisites are not met on a training day, this does not give rise to any claim to a make-up session or refund.
The regular price is EUR 2,450 plus statutory VAT per person and is due for payment after conclusion of the contract, unless otherwise agreed. Incidental costs for accounts, API usage, and optional servers (approx. EUR 50–80 according to the prerequisites page) are borne by the participant and are not part of the training fee. As an alternative to the training fee, a contribution of 2.5 working days to a SPICEy3 project may be agreed ("time for time"). Scope and details are agreed individually in writing before the training starts.
If the participant withdraws, the following applies unless otherwise agreed: up to 21 days before the start of the training, free of charge; up to 7 days before the start of the training, 50% of the training fee; thereafter or in case of non-attendance, 100% of the training fee. Rebooking to another date is possible once free of charge up to 7 days before the start of the training, thereafter by arrangement. If SPICEy3 has to cancel a date (e.g. due to insufficient participants), amounts already paid are refunded in full; further claims are excluded.
All materials provided in the training (slides, templates, exercise materials, sample solutions) are protected by copyright and intended for the participant's personal professional development. Without prior written consent of SPICEy3, the following is not permitted: passing them on to persons who did not take part in the training themselves; using them to run own, in particular commercial, trainings or comparable offerings; publishing them or making them publicly accessible. If the participant submits own documentation to SPICEy3 during the training (e.g. learning or project slides), the participant grants SPICEy3 the right to use the insights contained therein – in anonymized form where necessary – to further develop future trainings. Confidential or personal project details must be removed or made unrecognizable by the participant before submission.
SPICEy3 treats the project content participants bring into the training as confidential and uses it exclusively to deliver the training, unless section 7, second paragraph (submission of own documentation) provides otherwise. Participants are advised not to bring real customer data or trade secrets into their training project (see the notes on choosing a project).
SPICEy3 is liable without limitation for intent and gross negligence and in accordance with the German Product Liability Act. For slight negligence, SPICEy3 is only liable for breach of an essential contractual obligation (cardinal obligation) and limited to the damage foreseeable and typical for the contract at the time the contract was concluded. Otherwise, liability is excluded. SPICEy3 assumes no liability for content and results that participants create themselves with AI tools during the training – responsibility for reviewing and releasing their own work results remains with the participant or their company.
The law of the Federal Republic of Germany applies. Place of jurisdiction for all disputes arising from this contract is, to the extent permitted by law, the registered office of SPICEy3. Should individual provisions be invalid, the validity of the remaining provisions remains unaffected.
As of: October 2026. SPICEy3 Consulting GmbH (i.G.), Wiesenweg 3, 26434 Wangerland.