io.github.sionjang101-create/taskattest
Related Servers
Alternatives to io.github.sionjang101-create/taskattest
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to enforce spec-driven development and verify code before it is marked done, using six tools that catch invented APIs, scan for hallucinated content, check plugin conformance, sandbox-run tests, validate schemas, and record audit evidence.771 npm8PolyForm Noncommercial 1.0.0
- AlicenseBqualityBmaintenanceChecks AI agents' claims against primary evidence, with no model; observes only what you grant.8108 PyPIApache 2.0
- AlicenseBqualityCmaintenanceEnables coding agents to run budgeted tests and checks under a countdown with a stop rule, shape long logs into concise failure summaries, and guard pre-existing test files against silent assertion rewrites. It also delivers relevance-filtered project memory and renders a token-and-time roadmap of the orchestrator and every subagent spawned for a task.7MIT
- AlicenseCqualityCmaintenanceA fail-closed preflight, approval, evidence, and verification runtime for agents, preventing unsupported output from being treated as verified completion.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to run deterministic completeness audits on code before declaring 'done'—catching unwired modules, placebo tests, swallowed errors, and stubs via AST analysis, entirely offline and free.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and orchestrators to deterministically verify sub-agent outputs inside the loop, catching placeholders, unbacked claims, stale state, count mismatches, and missing components before acting on claimed completion. It also supports failure reports and hash-chained verification receipts.1MIT
TDQS
Scored across 4 tools
Each tool has a distinct role: describe_checks is reference/help, draft_spec authors a spec, verify_task runs the judgement, and replay_evidence audits an existing manifest. The only mild overlap is verify_task vs replay_evidence, since both 'verify', but the descriptions clearly separate live verification from re-checking a recorded digest. describe_checks and draft_spec both touch spec content, but one documents check types and the other generates a draft, which the descriptions make explicit.
All four names follow a clean verb_noun snake_case pattern: describe_checks, verify_task, replay_evidence, draft_spec. No mixed conventions or vague stand-alone verbs.
Four tools is squarely within the well-scoped range and each maps to a necessary step in the workflow: learn the checks, draft a spec, verify, and replay. Nothing appears redundant or padding.
The discover-draft-verify-replay loop covers the core lifecycle of deterministic spec-based task verification. Minor gaps remain: there is no tool to finalize or edit a spec (removing the draft flag is left to a human out-of-band) and no way to list or discover existing evidence manifests, so callers must already know paths.