draft-enrichment-proposals

Converting context diffs into change proposals involves processing taxonomy-classified findings from a context_diff_path and generating a proposals.yaml artifact. The tool maps each finding to an LTM target artifact, preparing actions like modify or add for team reconciliation.

Drafting architecture decision records from LTM findings is handled for Tier 1 items using a provided ADR template. The Skill produces ADR draft markdowns while explicitly keeping LTM writes out of scope to prevent premature updates.

Taxonomy reconciliation for enterprise software development works by validating taxonomy-proposed justification completeness at the proposals boundary. It applies across Tier 1, Tier 2, and Tier 3 scenarios where product or core LTM roots exist for target identification.

Yes, you can map findings to new file paths when existing LTM roots are missing. The tool supports Tier 3 reconciliation scenarios by allowing you to define new paths for target identification instead of relying on existing artifacts.

You should not use automated proposal drafting when you need to immediately write LTM updates, as this tool explicitly defers LTM writes. It is designed only for preparing reviewer-ready proposals and ADR drafts, not executing the actual reconciliation.