| name | requirements-finalizer |
| description | Author phase-F per-file `requirements.md` for ONE mainframe or IBM i (AS400) source from its prepared section drafts. LLM-driven. USE FOR: assemble IBM i or mainframe technical requirements, stitch REQ sections, and phase-F finalization. DO NOT USE FOR: per-section authoring, index/complete, QA, or portal build. |
| argument-hint | Source file path + optional --languages en,it. Writes docs/<lang>/<file>/requirements.md per language. The agent finalises by reading `_finalize.bundle.md` + the per-section drafts and emitting one stitched file per language. |
Requirements Finalizer (per-file, phase F)
LLM-driven phase-F finalizer. For ONE source file, stitches the per-section
requirements drafts written by requirements-writer
into a single, complete requirements.md per requested language. EN is the
source-of-truth; non-EN siblings are co-finalised in the same LLM call.
Status: implemented. The contract and bundle schema are pinned, and the
requirements-specific packager under scripts/ is implemented.
This is the per-file scope of the requirements family. The per-section
requirements-writer skill explicitly forbids authoring the final stitched
document; that scope lives here. The same agent
(requirements-writer.agent.md) handles both scopes — only the bundle input
differs.
When to Use
- Every per-section requirements draft for the file has been authored and
passed
qa-reviewer (kind: "requirements").
