tenfoldBY SIAMETRICSTENFOLD ACADEMY / Claude Code
Use coding agents inside a disciplined engineering workflow, with project context, tests and human control.
For Developers and engineering teams working with an approved repository and review owner.
Imagine the work
A possible exercise and the kind of review it invites. Your actual case is selected for the programme and approved data boundary.
Illustrative practice artifact
The session sequence
This is the working sequence. Timing, depth and the number of sessions are configured for your team.
Agree a repository, environment, permissions and safe tasks.
Capture architecture, conventions and commands in a project-context pack.
Plan, implement, debug, refactor or document a bounded change.
Run tests and static checks, examine threats and complete human code review.
Turn effective patterns into team standards and an adoption backlog.
Curriculum
Expand each module to see what the practice covers. Modules and exercises are selected and configured for the agreed audience and work.
Understand delegation, context, tool use and the limits of agent autonomy.
Describe architecture, conventions and the commands an agent should use.
Break a change into reviewable steps with explicit acceptance conditions.
Practise on a bounded task in the agreed stack and environment.
Show the evidence a reviewer needs and check that existing behaviour still works.
Choose and constrain tools to fit the task and team workflow.
Set permissions and boundaries; protect credentials and control risky operations.
Connect agent work to existing review, release and observability practices.
Deliver a reviewable change, then repeat the method on a second task.
More than the session
The work produced and the ability to repeat it matter more than attendance alone. We agree the artifacts and evidence for your programme.
Participant pack
Purpose, schedule, access checklist, safe-use rules and what to bring.
Relevant templates, cases, instructions and review rubrics.
A reviewed artifact, useful corrections and an agreed next practice.
Sponsor pack
Participation, work produced, barriers, manager feedback and next recommendations.
A workplace challenge, feedback and a second attempt; office hours and follow-up are included when contracted.
Continue practice, scope a repeatable workflow or stop where further work is not justified.
Beyond the session
Apply the method to a bounded backlog item. Bring friction, review notes and test evidence to an optional office hour or team-standards clinic.
What good looks like
The team can repeat the method on a second task with review and test evidence, and explain how it fits the existing development lifecycle.
Ready to take part
Development experience and an approved repository are expected. The client provides paid tool access, environments, engineering leads and security review. Credentials and production-release authority remain with the client.
Plan it around your team
Tell us the audience, the work and your constraints. We agree depth, duration, group size, tools, follow-through and commercial scope in the proposal.
Email a programme brief ↗