You are here:
implementation-agent
$199.00 / year
implementation-agent is HIRMOS’s main implementation extension. In Software Development Lifecycle terms, it sits after approved system design and phase scope exist and before delivery is complete, turning that approved design into governed implementation prompts, reviewable execution, phase-reviewed implementation results, verification evidence, and trustworthy implementation outputs that teams and AI agents can use with confidence.
implementation-agent
Turn approved system design into governed implementation outputs.
implementation-agent governs the implementation part of the Software Development Lifecycle. It helps teams take approved design truth and phase scope, execute implementation work under review, preserve evidence, and pause honestly instead of letting build work drift.
What it does
- Consumes trusted upstream truth from artifacts such as
_hirmos/artifacts/sot/and_hirmos/artifacts/phases/. - Generates bounded implementation prompts under
_hirmos/artifacts/prompts/. - Runs governed implementation execution with review and correction instead of uncontrolled retries.
- Captures implementation runtime context and trust artifacts under
_hirmos/artifacts/context/implementation-agent/. - Stores execution evidence and operational records under
_hirmos/artifacts/ops/. - Pauses honestly when implementation can no longer proceed safely or truthfully.
Why software teams use it
- It creates a disciplined bridge between approved design truth and actual implementation work.
- It makes AI-assisted build work easier to review because prompts, runs, and evidence are preserved.
- It reduces drift between approved scope and implementation activity.
- It helps human implementation teams and implementation-oriented AI agents work from the same approved truth.
Fast mental model
Key outputs
- Generated implementation prompts in
_hirmos/artifacts/prompts/ - Implementation runtime context and trust artifacts in
_hirmos/artifacts/context/implementation-agent/ - Execution records and verification evidence in
_hirmos/artifacts/ops/ - Implementation changes and outputs produced during approved execution
Best fit: projects that already have approved design artifacts and now need disciplined implementation planning, execution, review, and verification.
How this extension looks inside HIRMOS
FAQ
When should I use implementation-agent?
Use it when approved design scope already exists and you want governed implementation planning or execution.
Where it fits in the Software Development Lifecycle?
– After approved design exists: it starts once trusted upstream artifacts such as reviewed system design and approved phase scope are available.
– At implementation planning and execution: it governs prompt generation, implementation runs, review, correction, and verification.
– At implementation handoff: it preserves prompts, context, and evidence so human teams and AI agents can inspect what happened and continue responsibly.
What does it need before it can run well?
It works best when strong upstream design artifacts already exist, especially approved system design and approved phase scope.
What does it produce?
Its core outputs include implementation prompts under _hirmos/artifacts/prompts/, execution context under _hirmos/artifacts/context/implementation-agent/, operational records under _hirmos/artifacts/ops/, and implementation changes made during approved runs.
Who can use its outputs?
Its outputs are designed for both human implementation teams and implementation-oriented AI agents.
Does it keep retrying until something works?
No. Retry is bounded. When correction stops being honest or useful, the workflow should pause instead of pretending the issue is solved.