unicorn

Useful topic. One clear guideline issue: your top description is > A curated list of awesome tools, frameworks, standards, and resources for business, systems, and product analysis. The guidelines flag this exact "A curated list of awesome..." pattern as the wrong one - the top description should describe the subject, not the list itself. The paragraph right below it ("Business, systems, and product analysis turn stakeholder needs into...") is exactly the kind of subject description they want, so I'd move that into the blockquote and drop the "curated list of awesome" line.

The "📖 For comfortable reading: Web version" link also points to a GitHub Pages render of this same readme - the same content twice. I'd remove it or move it to a Footnotes section.

Smaller thing: "Analysis" on its own is a fairly broad entry name for a general list; something like "Business Analysis" might read clearer, though that's your call.

Both fixed, thanks.

The blockquote now describes the subject instead of the list:

Business, systems, and product analysis turn stakeholder needs into clear, verifiable requirements, designs, and product decisions.

I also trimmed the paragraph under it so it isn't saying the same thing twice. The web version
link moved down to a Footnotes section;

On the name, I'll try to keep Analysis. Business analysis is the biggest slice, but modeling
notations, integration and API analysis, and product analytics are a decent chunk of the list
and none of that is business analysis, so the narrower title would oversell one part of it.
But I agree, and one day it should be split when we have gathered enough knowledge of the specific analysis type.

Great list. In my opinion, the AI & Agentic Analysis is the weakest section in this tight list. Claude, ChatGPT, Gemini, DeepSeek and Qwen sit there with near-identical descriptions — all variations on "assistant for drafting requirements". A reader who needs to be told ChatGPT exists isn't the reader for this list, and five general-purpose chatbots will date faster than anything else here. The entries doing real work are Spec Kit, OpenSpec, ChatPRD and MCP, because those are specific to the analysis workflow. I'd cut the general assistants down to a line of prose or drop them. Separately, Awesome LLM Apps is an awesome list, so it probably belongs under Related Lists. 'Prompt Engineering Guide' would probably fit best in 'Learning Resources'.

Thanks both, @VictorOsondu and @mxuexxmy. You landed on the same section, so I reworked it.

I removed five general assistants, replaced by one line in the intro, and Cursor and Copilot went with them for the same reason. Awesome LLM Apps moved to Related Lists, Prompt Engineering Guide to Learning Resources. Added a few analysis-native things instead - the MCP registry, Atlassian's MCP server, Agent Skills.

Awesome LLM Apps moved to Related Lists and Prompt Engineering Guide to Learning Resources.
Both were misfiled, thanks for catching it.

On the name, I would suggest to keep Analysis, same reasoning I gave lesnik512 earlier: business analysis is
the biggest part, but systems and product analysis are a real chunk of the list and a narrower
title would misrepresent what's in it. All in all, i will be ready to rename it to Business Analysis as parent domain name, but lets postpone/sync this question with Sindre, please.

Hey! Great list. The topic is really solid and the formatting looks completely in line with the guidelines. One very minor thing I noticed is that some descriptions might be a tiny bit long - Sindre's guidelines mention keeping descriptions succinct (ideally fitting on one line if possible). Other than that, everything looks perfect, including the awesome-lint passing status. Nice work!

@jordanricky1604-ship-it Thanks for the review! trimmed the long ones were over the line, so every entry renders on a single line

The README still ends with a CC0 badge and waiver sentence. The current submission requirements explicitly say not to add the license name, text, or a License section to the README because GitHub already exposes the root license file. Since the repository already has a LICENSE file, I would remove that final badge and waiver block and let the root file carry the licensing information.

The README still ends with a CC0 badge and waiver sentence. The current submission requirements explicitly say not to add the license name, text, or a License section to the README because GitHub already exposes the root license file. Since the repository already has a LICENSE file, I would remove that final badge and waiver block and let the root file carry the licensing information.

thanks for raising it, updated the repo

Re the name, decided to keep Analysis. There are separate Business Analysis, Product Analysis and Integration Analysis sections in the list now, so Business Analysis as a title would cover only part of it.

Also rewrote the description at the top.

Thanks @lesnik512 @mxuexxmy for raising it