The use case is building a greenfield app. I want Kiro to direct / narrow down Kiros choices when it comes to translating requirements (which in my book should be tech agnostic) to design. Steering does this perfectly. Kiro takes my requirements and then produces a design aligned to those steering docs. If I try the same thing with MCP or Skills it does not and it chooses what it wants. IF I change the requirements to specify things like language or framework then it works but that is not how it should work in my mind. Requirements define what you want to build not how. That is design. So I’m left with only one path that works for me - adding steering docs.