Skip to main content
Glama
io.github.sionjang101-create/taskattest

io.github.sionjang101-create/taskattest

Related Servers

Alternatives to io.github.sionjang101-create/taskattest

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      8
      PolyForm Noncommercial 1.0.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      7
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      A fail-closed preflight, approval, evidence, and verification runtime for agents, preventing unsupported output from being treated as verified completion.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues