What problem does it solve? Turning a settled design into a well-formed implementation issue is error-prone: links break after branch deletion, code internals leak into analyst-facing text, and issues get filed prematurely. This Skill enforces a draft-validate-publish pipeline so every change request in Netcracker/qubership-envgene is bounded, link-stable, and publish-ready before it is filed. ## Core Features & Use Cases - Two seeding sources: Parse an existing design doc or doc PR, or synthesize a draft from the working conversation and code investigation, with one shared downstream pipeline. - Dry-run drafting with iteration: Produces a local Markdown draft first, re-reads it every turn to preserve hand edits, and files only after explicit user confirmation. - Link rigor and pre-file gate: Requires commit-SHA permalinks and PR references that survive merges, plus a mechanical checklist blocking code references, undocumented identifiers, and house-rule violations. - Use Case: After finalizing a feature design doc PR, ask to file a CR; the Skill parses the doc, drafts the six-section issue body with per-item anchor links, iterates with you, then creates the typed GitHub issue via MCP tools. ## Quick Start Ask the assistant to turn the settled design doc PR into a change request issue in qubership-envgene and review the local draft before saying file it.
