feature-writer

Drafting feature pages with auditable references requires mapping real surfaces to concrete guarantees across hero and sections, producing a YAML-ready narrative that supports discovery, search, and governance review.

Structuring feature documentation for marketplace publication involves capturing Why/What/How sections, surface-to-guarantee mappings, and an auditable trail within a YAML-ready Markdown format.

Generating per-feature reports that map code references to verifiable guarantees is possible through a research-first drafting workflow that aligns outputs with governance standards and source-backed verification.

Ensuring feature writing passes governance review requires automating reference verification during drafting, explicitly mapping claims to real surfaces and code references for an auditable trail.

Feature page content fails governance checks when claims lack explicit mappings to real surfaces and verifiable references, missing the auditable trail required for governance-aligned structure and review.

YAML-ready metadata is required to publish feature pages with governance compliance, as it supports discovery, search, and governance review alongside the Markdown narrative content.