Live data from Hacker News

Show HN: QUALITY.md – open format/specification, agent skill, and CLI

getquality.md

1–10 of 30 posts

Show HN: QUALITY.md – open format/specification, agent skill, and CLI

#1
Hello all, I created QUALITY.md to help build a holistic quality evaluation process for my projects. Turns out it's also ideal for loop engineering. I'm hoping this provides a valuable contribution to the conversation around quality and craft and having AI help us in the effort. I hope to shift the mindset from a reactive/review/repair mindset to a proactive care mindset.

Give it a go. I look forward to your thoughts/comments/feedback!

Website: https://getquality.md GitHub: https://github.com/qualitymd/quality.md

Show HN: QUALITY.md – open format/specification, agent skill, and CLI
getquality.md

Re: Show HN: QUALITY.md – open format/specification, agent skill, and CLI

#2
The one thing I do not understand is that here you say:

"Ensure stakeholders are aligned on what matters most and why"

But it is instructions for LLMs, right? A way to describe something that the humans know and the LLMs don't.

LLMs literally cannot be stakeholders, by definition.

Re: Show HN: QUALITY.md – open format/specification, agent skill, and CLI

#4
post #2

The one thing I do not understand is that here you say: "Ensure stakeholders are aligned on what matters most and why" But it is instructions for LLMs, right? A way to describe something that the humans know and the LLMs don't. LLMs literally cannot be stakeholders, by definition.

Not OP, but it seems to me the idea is that stakeholders can collaborate and come to consensus on the contents of QUALITY.md.

Re: Show HN: QUALITY.md – open format/specification, agent skill, and CLI

#7

Is this really where we've landed? I refuse to believe that any of this markdown insanity will continue indefinitely.

it's looking like llms are interpreters, and markdown plus english text is the language of choice to run non deterministic programs on it

Re: Show HN: QUALITY.md – open format/specification, agent skill, and CLI

#9

Is this really where we've landed? I refuse to believe that any of this markdown insanity will continue indefinitely.

it is until we define real consistent deterministic gates and protocols. It really is a symptom of the lack of concerted effort. Everyone has a personal preference on how to shove the context and most of them are just "here's some good text I've found to work in my context"
Post reply on HN