resolve-grill-anchor

To lock a grilling anchor, resolve an epic, feature, or design-decision identifier into a concrete product LTM file and inventory every downstream cross-referenced touchpoint. This prevents round-by-round discovery by precomputing declared constraints and failure scenarios before questioning begins.

Deterministic anchor resolution validates allowed anchor_kind values, then extracts constraints, business rules, and failure scenarios from the resolved product LTM file. For epic and feature anchors, it also extracts success scenarios to ensure comprehensive defensive preparation.

Inventory cross-referenced artefacts by walking the product reference graph conservatively to enumerate every target-shape artefact impacted by the anchor. This produces a complete downstream touchpoint set required for an atomic session close bundle.

Intent-driven development uses YAML inventory files for SDLC governance by writing anchor-lock.yaml and downstream-touchpoints.yaml as STM artefacts. These files are placed in the configured issue evidence or grill-me directory to maintain declared constraint traceability.

You can use it with tech-decision and design-decision identifiers in addition to epics and features. The resolution validates allowed anchor_kind values and adapts guardrail extraction, only pulling success scenarios for epic and feature anchors.

Walking cross-references conservatively limits the downstream impact inventory to declared target-shape artefacts only, preventing speculative enumeration. This ensures the touchpoint set remains grounded in validated product references rather than inferred dependencies.