system-design-agent

Turn software requirements into trusted system design artifacts.

system-design-agent governs the part of the Software Development Lifecycle that sits between raw software requirements and implementation. It helps teams move from unshaped requirements to reviewed system design, architecture direction, phase contracts, and staged delivery plans before build work begins.

What it does

• Normalizes raw software requirements and approved upstream design signals.
• Produces trusted design artifacts under _hirmos/artifacts/sot/.
• Generates approved phase contracts under _hirmos/artifacts/phases/.
• Captures design-cycle traces, normalized runtime context, and unresolved-item trust artifacts under _hirmos/artifacts/context/system-design-agent/.
• Pauses when unresolved items need Orchestrator review instead of letting weak assumptions flow downstream.

Why software teams use it

• It brings structure and reviewability to the part of the lifecycle where requirements and design decisions often become messy or implicit.
• It creates a governed handoff between pre-build thinking and downstream implementation.
• It makes design outputs easier for implementation teams and AI agents to use independently.
• It can be enriched by supporting extensions such as prototype-ingestion and presentation-design.

Fast mental model

Key outputs

• Trusted system design artifacts in _hirmos/artifacts/sot/
• Generated phase contracts in _hirmos/artifacts/phases/
• Design-cycle traces, unresolved-item trust artifacts, and normalized runtime context in _hirmos/artifacts/context/system-design-agent/

Best fit: projects that need disciplined requirements analysis, system design, architecture direction, and staged delivery planning before implementation begins.

How this extension looks inside HIRMOS

FAQ

When should I use system-design-agent?
Use it when your project needs governed requirements analysis, system design, architecture direction, phase design, or staged delivery planning before implementation begins.

Where it fits in the Software Development Lifecycle?
– After requirements emerge: it starts once raw software requirements and other approved upstream signals are available.
– Before implementation begins: it governs requirements clarification, analysis, system design, architecture direction, phase design, and staged delivery planning.
– At implementation handoff: it produces reviewed outputs that implementation teams and AI agents can use with less ambiguity.

What does it produce?
Its core outputs include trusted design artifacts under _hirmos/artifacts/sot/, approved phase contracts under _hirmos/artifacts/phases/, and design-cycle traces plus normalized runtime context under _hirmos/artifacts/context/system-design-agent/.

Who can consume its outputs?
Approved outputs can be used by human implementation teams, implementation-oriented AI agents, and compatible downstream extensions.

Can supporting extensions enrich it?
Yes. prototype-ingestion and presentation-design can contribute normalized upstream signals before design continues.

Does it keep going when important answers are missing?
No. Serious design cycles can pause so the Orchestrator can review unresolved items and decide how to proceed.