product-cli MCP server
Commit Nov 11, 2026Manages product features, ADRs, and test criteria as a machine-checkable knowledge graph for decision-driven design.
Also known as Hafeok/product-cli
- Stars
- 6
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
What is product-cli MCP?
product-cli manages product features, ADRs, and test criteria as a machine-checkable knowledge graph for decision-driven design.
Summary generated from the project's README
About product-cli MCP server
Defining product features, architecture decision records, and test criteria as a machine-checkable knowledge graph is what product-cli enables for decision-driven design. Instead of using prose and diagrams, users author the product specification using the sdlc: vocabulary through nodes, edges, and shapes. This approach ensures that any requirement that cannot be expressed as a graph element is flagged as unspecified.
Developers use this tool to simulate behavior through Deciders and Projectors against specific scenarios before any actual code is written. The system produces a canonical document that serves as an executable oracle for product behavior. It is built as a Native AOT .NET binary, requiring the .NET SDK for building and specific platform toolchains like clang, Xcode, or Visual C++ for publishing to linux-x64, linux-arm64, osx-arm64, or win-x64. The tool focuses on the specification layer and does not dictate how the final code is realized.
What you can do with it
- 1Formalize product specificationsConvert vague product requirements into a structured graph of nodes and shapes to ensure every feature is explicitly defined.
- 2Simulate product behaviorTest how a product should behave by running Deciders and Projectors against scenarios before writing implementation code.
- 3Trace design decisionsMaintain a history of who adopted specific graph elements during the collaborative authoring process.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablehafeok/product-cli is public and reachablegithub.com/hafeok/product-cli ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/hafeok/product-cli ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubproduct-cli
A machine-checkable statement of what a product does, with an executable
oracle for its behaviour, exported as one graph that someone else can sign.
product-cli is being rewritten as one Native AOT .NET binary that authors that
statement — the What of a product, in the sdlc: vocabulary — as a graph with
shapes, never prose with diagrams. Anything that cannot be stated as a node,
an edge or a shape is not yet specified, and the tool says so rather than
accepting it.
The What is authored in conversation: an agent proposes, the author watches the graph, its findings and its open questions change live, and adopts or rejects each proposal, so every element traces to the person who adopted it. Behaviour is executable before any code exists — Deciders and Projectors are simulated against scenarios drawn from the flows, and the same scenarios later judge realised code through a wire protocol. The tool puts nothing in force and decides nothing about realisation: it produces a canonical document, and what that document is held against, and who accepts it, belong to Writ.
Definition
The product is defined in decision-driven-design:
applications/sdlc/product-cli/product-definition.md.
This repository holds the tool, its ADRs (docs/decisions/) and its tests.
Agents start at AGENTS.md.
Build and test
The repository is the skeleton of slice 0 (D1.25): the eight layer projects
under src/, their tests under tests/, and a host whose only behaviour is
product --version. It needs the .NET SDK that global.json pins (10.0.401,
or a later feature band of 10.0) and nothing else.
dotnet build ProductCli.slnx -c Release
dotnet test -c Release --no-build
The tests build probe projects with dotnet build against the solution's
outputs, so build the solution first.
To publish the native binary, product, for your platform: Native AOT
compiles for the operating system it runs on, and needs that platform's
native toolchain (clang on Linux, Xcode on macOS, the Visual C++ build tools
on Windows).
dotnet publish src/ProductCli.Host/ProductCli.Host.csproj -c Release -r linux-x64 -o artifacts/publish/linux-x64
artifacts/publish/linux-x64/product --version
The supported runtime identifiers are linux-x64, linux-arm64, osx-arm64
and win-x64.
The Rust tool
The Rust workspace is frozen at the tag
rust-final
(commit 70395df), where all of it stays readable under the MIT licence it
was published with. No Rust release follows it. Its published releases, up to
v0.7.0,
keep working.
Licence
Apache-2.0 (LICENSE, NOTICE). Developed with AI
assistance under human review.
product-cli MCP questions
What is the core purpose of product-cli?
It provides a machine-checkable statement of what a product does using a knowledge graph of shapes rather than prose and diagrams.
What technologies are required to build the tool?
You need the .NET SDK as specified in the global.json file.
Which operating systems are supported for the native binary?
The tool supports linux-x64, linux-arm64, osx-arm64, and win-x64.