I have found a lot of value in the approach the post describes. I store my markdown as GitHub issues, regardless of how I come up with a detailed feature description (usually a chat session).
Before implementation, context is always cleared to ensure that the model is working only from known context (skills, AGENT.md, etc).
A major benefit of this is that agents can look up prior prompt instructions as needed or when mentioned in the current prompt it's working on.
I recently described my workflow here <a href="https://jaisenmathai.com/articles/sojourn-for-ios-was-45-one-shot-prompts/" rel="nofollow">https://jaisenmathai.com/articles/sojourn-for-ios-was-45-one...
jmathai · · focus · HN ↗
Before implementation, context is always cleared to ensure that the model is working only from known context (skills, AGENT.md, etc).
A major benefit of this is that agents can look up prior prompt instructions as needed or when mentioned in the current prompt it's working on.
I recently described my workflow here <a href="https://jaisenmathai.com/articles/sojourn-for-ios-was-45-one-shot-prompts/" rel="nofollow">https://jaisenmathai.com/articles/sojourn-for-ios-was-45-one...