---
title: "Discussion on \"ANSS: A Specification Standard Built for AI Agents, Not Just Humans\" | Hashnode"
description: "Discussion on \"ANSS: A Specification Standard Built for AI Agents, Not Just Humans\". Open spec standard that reduces ambiguity-driven errors in AI-assisted development. Invariants, Agent Review, 3-layer markup. Free on GitHub."
url: "https://hashnode.com/posts/anss-a-specification-standard-built-for-ai-agents-not-just-humans/6a20c26c0b1b181bac28fc35"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [ANSS: A Specification Standard Built for AI Agents, Not Just Humans](https://kholomyanskiy.hashnode.dev/anss-a-specification-standard-built-for-ai-agents-not-just-humans?utm_source=hashnode&utm_medium=feed)

Open spec standard that reduces ambiguity-driven errors in AI-assisted development. Invariants, Agent Review, 3-layer markup. Free on GitHub.

Jun 4 · 2 min read · kholomyanskiy.hashnode.dev  
Updated Sep 21  
Read the article

-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#software-development](https://hashnode.com/tag/software-development)
-   [#specification](https://hashnode.com/tag/specification)
-   [#claude-code](https://hashnode.com/tag/claude-code)
-   [#cursor](https://hashnode.com/tag/cursor)

## Written by

[Artem Kholomianskyi](https://hashnode.com/@kholomyanskiy)

@kholomyanskiy · Elblag, Poland

  
[View profile](https://hashnode.com/@kholomyanskiy)

AI Implementation Consultant · client side

11 years in energy-sector IT on the client side: requirements for vendors, supervision and acceptance of rollouts (SAP IS-U, SCADA, OMS/DMS). Since 2023 the same discipline applied to AI and automation projects. I write about specifications, acceptance criteria and what breaks before the first line of code.

## Responses 4

Markdown supported · ⌘↵ to post

[Adam Lewis](https://hashnode.com/@nark3d)

[Jun 7](https://hashnode.com/posts/anss-a-specification-standard-built-for-ai-agents-not-just-humans/6a20c26c0b1b181bac28fc35/comment/6a25a46cf416d1b56e8dcaa5)

We've kept the runnable check as the load-bearing part of our specs too. Without it the agent grades itself generously on what "done" means.

Have you found agents actually read the \[A\] layer first when prompted, or does it need a hook to enforce the order?

[Artem Kholomianskyi](https://hashnode.com/@kholomyanskiy)

[Jun 7](https://hashnode.com/posts/anss-a-specification-standard-built-for-ai-agents-not-just-humans/6a20c26c0b1b181bac28fc35/comment/6a25a46cf416d1b56e8dcaa5#reply-6a25ae987829edb31110654b)

That’s exactly it - without the Check field, “done” means whatever the agent decides it means. On the \[A\] layer: I don’t rely on reading order. Agent Review is the real enforcement - if the agent can explain the invariants before coding, it processed what matters.

[Adam Lewis](https://hashnode.com/@nark3d)

[Jun 9](https://hashnode.com/posts/anss-a-specification-standard-built-for-ai-agents-not-just-humans/6a20c26c0b1b181bac28fc35/comment/6a25a46cf416d1b56e8dcaa5#reply-6a27dc1d7993365ef980671c)

Makes sense. I've found the same thing - getting the agent to say the invariants back before it writes anything surfaces a misread while it's still cheap to deal with. The one place I'd be careful is that it tells you it understood, not that the code does the right thing. I've had it restate a rule perfectly and then break it two functions later. So I treat the explain-back as the check on whether it read the brief, and keep a runnable test for whether the code actually holds to the rule once it exists.

[Artem Kholomianskyi](https://hashnode.com/@kholomyanskiy)

[Jun 10](https://hashnode.com/posts/anss-a-specification-standard-built-for-ai-agents-not-just-humans/6a20c26c0b1b181bac28fc35/comment/6a25a46cf416d1b56e8dcaa5#reply-6a28a934fdcbdbcd01f519a4)

Exactly right. Explain-back checks parsing, not compliance. I treat ANSS invariants as the spec for the test - if INV-001 says "no node\_modules imports", that's what the test asserts. Cheap pre-check, not a substitute for the real thing.
