projtruth
Related Servers
Alternatives to projtruth
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceRequirements knowledge base for coding agents, stored per Git branch in your repo, with Prolog checks for contradictions, untraced code and unproven requirements.1612AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to link spec acceptance criteria to the tests that cover them, list requirements, trace coverage, find gaps, and generate failing test stubs.MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents structured tools to maintain a living requirements traceability graph — requirements to user stories, cucumber scenarios, screens and phase results — so coverage and its trend across releases can be queried on demand and explored through a web dashboard.33 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnforces protocol-driven development by validating requirements, designs, scope, and acceptance evidence, while maintaining immutable, traceable governance archives.-
- AlicenseAqualityBmaintenanceEnables tracing every code change to a requirement and every requirement to a test that actually exercises it, with gap analysis, coverage, change-impact mapping, and evidence reports for Python and C/C++. Enforces human-only sign-off and an independent reviewer that cannot edit code, so AI-written changes can be audited and reproduced.12Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents and developers to independently verify code and documentation claims against the repository, producing evidence-backed audit reports and pull-request checks.14MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct resource+action pair: decisions (decide vs decisions_list), requirements (req_add, req_scope, req_set_status, req_list), evidence (evidence_scan), and reporting (status_report). The only mild overlap is req_list vs status_report, but descriptions clarify that one shows declared registration data while the other shows computed status plus evidence. No tool appears to duplicate another.
Most tools follow a noun-prefixed grouping convention (req_add, req_scope, req_set_status, req_list, decisions_list, evidence_scan, status_report), which makes the families readable, but the bare verb `decide` breaks the pattern and `req_set_status` mixes noun+verb+noun while `decisions_list` and `status_report` are noun+noun. The set is still understandable but not a single predictable verb_noun scheme.
Eight tools is well within a healthy range and each addresses a distinct part of the requirement/decision/evidence lifecycle. Nothing feels padded or redundant; every tool has a clear role in the workflow.
The core lifecycle is covered (capture requirements, scope, set status, read; log and read decisions; scan evidence; report status), but there is no way to update or delete a requirement, remove or amend a decision, or edit criteria after creation. Writing evidence files is implied to happen outside the tool surface, which is a deliberate but notable gap for agent workflows.