AI Engineering Journey
Public Python tool · design and implementation
What has to change before a team can delegate more?
I built AI Engineering Journey to turn an organisation’s capability assessment into a focused 90-day roadmap. It examines discovery, workflow, evaluation, architecture, platform, governance, and learning, then identifies the capabilities constraining progress.
The interesting engineering choice is to make the evidence visible. A later assessment is compared with the earlier priorities, so a higher self-reported score is distinguishable from a demonstrated improvement. A workflow-readiness check shows where an agentic pipeline would have to stop for human intervention.
This is a decision-support tool. Its scores depend on the assessment supplied; it does not independently audit an organisation or certify autonomous delivery.
Three stages from autocomplete to agentic-scale delivery.
AI-augmented
Engineers use AI for explanation, refactoring, tests, and local implementation help. Productivity improves, but the process is still centered on individual prompting.
The model proposes. The harness disposes.
Spec, plan, implement, validate, replan.
Constitution
Capture mission, architecture, constraints, coding standards, and non-negotiables.
Feature spec
Define outcome, edge cases, acceptance tests, and what must not change.
Agent plan
Ask the agent to decompose work before touching files or running tools.
Implementation
Delegate bounded tasks with clear permissions, context, and test commands.
Validation
Review diff, tests, trace, cost, rollback path, and the next replan.
Forward the constraint before the capability.
Use autonomy where evidence is inspectable.
Parallel agents can cover more ground, but they also consume more context and compute. The discipline is to name cost, failure modes, and stop conditions before the architecture becomes fashionable.