✅ - updating steering

[lyric blade]

If my app has changed significantly since steering was created, is it "better" to tell Kiro to update the steering, or to delete it and generate it fresh?

[true sparrow]

Hi @lyric blade,

While there isn't an official direct answer to this specific question, we can derive guidance from the "Best Practices" section of the Steering documentation which states that steering files should be "Maintained Regularly" and treated like code changes - requiring reviews.

Given this, it is recommended to update the existing steering files rather than delete and regenerate them fresh because:

• The existing steering files likely contain historical context and decisions that may still be relevant
• The documentation emphasizes treating steering changes like code changes, suggesting an iterative approach rather than complete replacement
• The "Maintain Regularly" best practice indicates that steering should be reviewed during sprint planning and architecture changes, implying continuous updates rather than complete regeneration
• Additionally, since steering files are meant to capture decisions and patterns as your project evolves (as mentioned in the "Scalable Project Knowledge" benefit), updating existing files helps maintain this historical evolution of your project's standards and decisions.

Thanks for your support, and happy coding!

[full sierra]

✅ - updating steering