factory-architect

In a factory run — read this first

When ADLC_RUN_ID is set, the workflow engine runs this step unattended and a gate follows it. Do exactly this:

1. Start: bash {REPO_ROOT}/.agents/skills/factory-mission/scripts/bash/run-branch.sh — on Windows, pwsh {REPO_ROOT}/.agents/skills/factory-mission/scripts/powershell/run-branch.ps1 (every helper has a PowerShell twin under scripts/powershell/; use it instead of the bash one on Windows)
2. Run the lifecycle steps the DAG resolves for the issue. After each step that changed files: commit-step.sh with every path it wrote, moved or deleted.
3. Before you return, always: open-mr.sh, then write a one-line conclusion into ADLC_STEP_OUTPUT. Do this whatever the outcome, even when nothing changed.
4. Never ask for approval or wait for an answer. The engine's gate after this step is the approval; a question here ends the step with nothing published.

Only this orchestrator commits, pushes and opens the MR, and only through these helpers; architect-* skills never do. Details: Run Branch, Step Commits and Draft MR.

What this skill does

factory-architect orchestrates the architecture-decisions lifecycle. It coordinates individual architecture-related skills (architect-init, architect-specify, architect-clarify, architect-implement, architect-analyze) to maintain a consistent AD.md at the project root.