doc-claim-verification

Sterne19

Forks2

Aktualisiert24. Juli 2026 um 00:30

Pointer stub — per-document doc-vs-code claim verification is owned by the architecture-conformance-auditor agent, which emits HOLDS/DRIFT/VIOLATION/PHANTOM/UNDOCUMENTED verdicts with evidence natively. Dispatch it via the architecture-refresh pipeline instead of following prose steps here.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

woojubb

woojubb/robota

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige ComputerberufeInformatik- und Mathematikberufe·SOC 15-1299

SKILL.md

readonly

name	doc-claim-verification
description	Pointer stub — per-document doc-vs-code claim verification is owned by the architecture-conformance-auditor agent, which emits HOLDS/DRIFT/VIOLATION/PHANTOM/UNDOCUMENTED verdicts with evidence natively. Dispatch it via the architecture-refresh pipeline instead of following prose steps here.

Doc Claim Verification (pointer)

This behavior is owned by the architecture-conformance-auditor agent: it verifies architecture documents' claims against code in both directions and classifies each claim (HOLDS / DRIFT / VIOLATION / PHANTOM / UNDOCUMENTED) with file:line evidence, natively.

Dispatch it via architecture-refresh (or standalone by agentType: architecture-conformance-auditor). Entry point: architecture-conformance-audit.

Mehr aus diesem Repository

gleiches Repository

delegated-refactor-green-gate

woojubb/robota

Pipeline for delegating one large mechanical change to a worker under a hard green-or-report gate — specify, dispatch mechanical-refactor-worker, independently re-verify the green claim, hand the working-tree diff to pr-review-reviewer, then commit. Route-only: it does no editing and forms no verdict. Use when delegating a big decision-free change on your own working tree.

2026-07-2619

worktree-parallel-orchestration

woojubb/robota

Procedure for running multiple independent backlog items in parallel via worktree-isolated subagents with zero merge conflicts — partition file ownership before spawning, isolate each implementer in its own worktree, sequence overlapping work behind occupants, one coherent self-verified PR per agent, and serial orchestrator merge. Use when executing 2 or more independent items concurrently.

2026-07-2619

architecture-conformance-audit

woojubb/robota

Thin router for the doc-vs-code architecture conformance audit (GATE-CONFORMANCE). Routes to the mechanical conformance scan plus the architecture-refresh agent loop (architecture-conformance-auditor / architecture-auditor + fixers), which own the audit behavior natively. Use before a release, after cross-package work, or when GATE-CONFORMANCE runs.

2026-07-2519

post-implementation-checklist

woojubb/robota

Router for the mandatory post-implementation sequence — SPEC sync, build/test, README, commit/PR, publish, content/ docs, docs deploy. Each step's detail lives in its owning skill/rule; this file only fixes the order and the gates. Execute automatically after implementation work; do not wait for the user to request it.

2026-07-2519

backlog-pipeline

woojubb/robota

Orchestrator for the spec document gate pipeline. Reads current status from frontmatter, determines the next gate, invokes backlog-writer or backlog-gate-guard, and updates frontmatter status on PASS. Does nothing else.

2026-07-2519

spec-code-conformance

woojubb/robota

Mandatory verification loop after any SPEC.md or contract document change. Compares spec against implementation code, fixes code to match spec, repeats until zero discrepancies, then runs regression tests. Spec is always the source of truth — never modify the spec within this workflow.

2026-07-2519

Jeden Skill mit einem Klick ausführen