# Finalize Promoted Knowledge

> Use when every Solution-Architect clarification question is resolved and the promoted draft documents must become settled product knowledge: flipping each promoted document's lifecycle status from draft to approved, marking register rows finalized, and setting the target's status record to a passing result. This is the finalize_promoted_knowledge action of the design stretch — one Agent-tool dispatch with subagent_type solution-architect (business-analyst and documentation-steward supporting) — the sign-off that promote-to-product-knowledge deliberately withheld.

- Skill: `bhangeef16/finalize-promoted-knowledge` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bhangeef16/finalize-promoted-knowledge`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bhangeef16/finalize-promoted-knowledge/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: BhangeeF16 (https://skillmd.com/u/bhangeef16)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bhangeef16/finalize-promoted-knowledge

---


# Finalize Promoted Knowledge

Flip reviewed drafts to approved. This is the step that turns a filed proposal into product truth — for a pure knowledge update with no design work attached, this step (not a design document) is what closes the request.

## Dispatch

One synchronous `Agent`-tool call, `subagent_type: solution-architect`, with `business-analyst` and `documentation-steward` named in the prompt as supporting lenses.

## Required inputs

- The promoted requirement register in draft status.
- The resolved Solution-Architect open questions from clarify-requirements.

## Required outputs (all mandatory)

- Each promoted document's lifecycle status flipped from draft (`Requirements`) to `Approved`.
- Requirement-register rows marked finalized.
- The target's status record set to pass or pass_with_risks, with blocking questions confirmed empty.
- The destination folder's README index confirmed current for every finalized document.

## Rules — draft-state discipline (closing half)

- Nothing flips to `Approved` while any Solution-Architect question is unresolved — zero open questions is the precondition, not a preference.
- Do not skip the status flip because the design work itself feels done; a draft-status document left behind after the run moves on is an unfinished job.

## Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).