wagneripjr
UserClaude Code plugin marketplace: 8 engineering skills (wagner-skills) + a 14-skill reverse-engineering pipeline that turns a legacy codebase into traceable, ATDD-ready specs (doc-this).
Categories
Indexed Skills (25)
doc-this-architect
Fourth agent in the doc-this Discovery pipeline (synthesis). STRICTLY DESCRIPTIVE — synthesizes C4 diagrams, full ERD, integration map, spec-impact matrix as factual dependency map. Uses LSP (outgoingCalls, incomingCalls, goToImplementation, workspaceSymbol) for deterministic dependency mapping when available; falls back to Understand-Anything layers/edges or LLM synthesis. Emits external-surface.json catalog covering every HTTP/gRPC/WebSocket/CLI/message/UI/job surface — ui entries one-per-page from the file manifest (never 'pages grouped by module'; controls get subkind:control + mounted_in). Merges Data Master's kind:database entries for external/mixed DBs. Binary confidence: 🟢 (citation) / 🔴 (gap). Dispatched programmatically by doc-this after Detective — never auto-triggered by user phrasing; direct '/doc-this-architect' is for resume/debug in an initialized pipeline. NOT for surface mapping. NOT for spec generation (doc-this-writer). NOT for technical-debt analysis.
doc-this-code-analyst
Second agent in doc-this Discovery pipeline (analysis). STRICTLY DESCRIPTIVE — describes code, never proposes improvements. Uses LSP for deterministic symbol inventory when available; falls back to Understand-Anything or direct reading. Per module: control flow, algorithms, data structures, metadata. Reads EVERY source file per module (markup, SQL, scripts — Total Source Coverage); token pressure checkpoints and resumes, never skips; large codebases may fan out reading to ≤3 Sonnet readers under explicit consent (verified before the ledger records). Binary confidence: 🟢 (file:line) or 🔴 (gap). No 🟡. Dispatched by doc-this after Scout — never auto-triggered by user phrasing; direct '/doc-this-code-analyst' is for resume/debug. NOT for surface mapping (doc-this-scout). NOT for business-rule interpretation (doc-this-detective). NOT for cross-module synthesis (doc-this-architect).
doc-this-data-master
Use as an optional Discovery agent that documents the legacy database completely — tables, columns, relationships, constraints, indexes, AND the DB-resident business logic legacy systems hide: views, stored procedures, functions, triggers, rules, computed columns, non-trivial DEFAULTs, DB-side scheduled jobs (pg_cron, SQL Server Agent). Branches on database_ownership: owned → schema + business-logic + migrations-timeline docs; external → external-contract.md treating consumed objects as frozen interfaces, emits kind:database entries with visibility:external_dependency for Architect's external-surface.json; mixed → both with per-object ownership; none → skipped. Profiles actual data (enum values vs code, null rates, orphans, rows-per-state) into data-profile.md when read access exists. Triggers: '/doc-this-data-master', 'analyze database', 'extract DB logic'. NOT a generic SQL formatter.
doc-this-design-system
Use as an optional Discovery agent that extracts design tokens from CSS/SCSS/LESS variables, Tailwind config, UI library themes (MUI createTheme, Chakra extendTheme, Mantine, Ant Design), styled-components/Emotion theme objects, Style Dictionary tokens.json, design-tokens.yaml, Storybook stories, and screenshots. Documents color palette (primary/secondary/neutral/feedback with full scale and hex/rgb/hsl values), typography (font families with fallbacks, scale, weights, line-height, hierarchy), spacing/grid/breakpoints, other tokens (border-radius, shadows, z-index, transitions, opacity), and the in-house component library when one exists. Triggers: '/doc-this-design-system', 'extract design tokens', 'document UI design', dispatched by doc-this when frontend has a design system. NOT for design generation. NOT for screen-by-screen UI documentation (doc-this-visor).
doc-this-detective
Third agent in doc-this Discovery pipeline (evidence-consolidation). STRICTLY DESCRIPTIVE — extracts cited business rules, decision traces from explicit sources, state machines, RBAC/ACL matrices. Uses LSP (incomingCalls, findReferences, goToImplementation) for deterministic API classification when available; falls back to Understand-Anything call-graph or heuristics. Classifies endpoints public/private in external-surface.json. Cross-references DB-resident logic from Data Master. Confidence binary: 🟢 (cited) / 🔴 (gap). Outputs domain.md, state-machines.md, permissions.md, decision-traces/. Dispatched programmatically by doc-this after the Code Analyst — never auto-triggered by user phrasing; direct '/doc-this-detective' is for resume/debug in an initialized pipeline. NOT for surface mapping. NOT for C4 synthesis (doc-this-architect). NOT for proposing improvements or labelling bugs.
doc-this-help
Use to get an analogy-driven explanation of every doc-this agent and when to use each. Covers all 12 Discovery agents with one-paragraph analogies (Scout = real-estate broker doing a walkthrough; Detective = Sherlock interpreting clues; Architect = cartographer producing formal maps; Reviewer = auditor stress-testing the contracts) plus the recommended sequence and customer-project safety notes. Triggers: '/doc-this-help', 'explain doc-this agents', 'which agent should I use for X', 'what does [agent] do'. NOT for actually running an agent — invoke that agent directly. NOT for the doc-this orchestrator (use it directly).
doc-this-promote
Use to stage doc-this Discovery output (.doc-this-sdd/) into the project's tracked SDLC chain — the single bridge and the only doc-this skill that touches docs/. Assigns next FR/NFR/ADR IDs (flat and compound), stamps OKF frontmatter (id/type/status/description + adrs/specs relation keys) on every promoted doc, writes docs/requirements/FR-NNN-[slug].md + ADR files, bootstraps docs/okf.yaml in legacy repos, regenerates index.md catalogs by dispatching okf-maintain and appends curated TRACEABILITY rows, generates ATDD 4-layer scaffolding (.feature files tagged @api/@browser/@database/@cli into the auto-detected runner — Reqnroll/Cucumber.js/playwright-bdd/behave/godog/cucumber-rs — plus DSL stubs and protocol-driver interfaces), prints a docs(FR-NNN) commit message, halts on collisions. Triggers: '/doc-this-promote', 'promote specs to docs', 'move the discovery output into docs', 'stage SDLC artifacts'. NOT for generation (doc-this-writer). NOT for review (doc-this-reviewer).
doc-this-reviewer
Sixth agent in the doc-this pipeline (review). Enforces describe-only pact — REJECTS pact violations. Validates 3 canonical files per unit, reclassifies confidence under binary 🟢/🔴, REJECTS 🟡/judgment phrasing/fabricated ADRs/technical-debt/NFRs-without-contract/bug-labels. Enforces ATDD discipline: public endpoint @api coverage, UI @browser coverage, private transitive coverage, cross-layer pairing, externally observable language. Validates citation quality (no UA paths or LSP operations as citations). Validates DB coverage for external/mixed, schema-version gate. Hard-REJECTs coverage failures (ledger⊉manifest, sampling phrases, grouped ui entries); spot-checks 🔴 gaps for answers in unread files. Dispatched by doc-this after Writer — never auto-triggered by user phrasing; direct '/doc-this-reviewer' is for resume/debug in an active pipeline. NOT for SDLC promotion (doc-this-promote). NOT for re-generation (doc-this-writer).
doc-this-scout
Use as the first agent in the doc-this Discovery pipeline (reconnaissance phase). Maps the surface of a legacy codebase: folder structure, languages and frameworks via config files (package.json, pom.xml, go.mod, Cargo.toml, *.csproj), dependency versions, package managers, application entry points, CI/CD configs, Dockerfiles, shallow database hints (Data Master goes deeper), test frameworks, and produces an organization-suggestion (module / use-case / endpoint / hybrid / feature) with rationale. Outputs .doc-this-sdd/inventory.md, dependencies.md, .doc-this/context/surface.json + file-manifest.json (Total Source Coverage ground truth) consumed by every downstream agent. Dispatched programmatically by doc-this after the first-run handshake — never auto-triggered by user phrasing; direct '/doc-this-scout' is for resume/debug in an initialized pipeline. NOT for deep per-module analysis (that's doc-this-code-analyst). NOT for database schema extraction (that's doc-this-data-master).
doc-this-tracer
Use as an optional Discovery agent that resolves 🔴 gaps via dynamic analysis when static analysis falls short. STRICTLY DESCRIPTIVE — cites log lines / span IDs / samples; never proposes fixes or labels behavior as wrong. Read-only — never executes mutating code. Sources: log files, distributed traces (OTLP, Jaeger, Datadog), anonymized production samples, error-tracker exports (Sentry, Bugsnag, Rollbar). Resolves gaps like actual state machines, caller payloads, dead endpoints, error rates. Also runs the 🟢 corroboration sweep: stamps Evidence provenance (static → static + runtime, artifact-cited) on telemetry-matched scenarios — hard-advisory when the legacy system cannot be run live. Updates .doc-this-sdd/dynamic.md; promotes 🔴→🟢 ONLY on a cited specific runtime artifact — otherwise the gap stays 🔴. No 🟡. Triggers: '/doc-this-tracer', 'analyze logs', 'mine traces'. NOT for live system probing or load testing. NOT for static-only analysis (doc-this-code-analyst/detective).
doc-this-viewer
Open a local viewer to browse doc-this output in a browser — navigate units (requirements/design/tasks), the external-surface catalog, C4/ERD/flowchart diagrams, coverage, and open gaps from the rich .doc-this-sdd/ staging tree, plus promoted SDLC docs (FR-NNN requirements, ADRs, TRACEABILITY, .feature specs) when present. Runs a co-located launch.mjs that builds a manifest and starts a localhost-only static server for a prebuilt Svelte app, then opens the browser; stop it with launch.mjs --stop. Triggers: 'view doc-this docs', 'open the documentation viewer', 'browse doc-this output', 'serve the docs', 'open .doc-this-sdd in a browser', '/doc-this-viewer'. NOT for generating docs — that's /doc-this. NOT for staging specs into docs/ — that's /doc-this-promote. NOT for UI screenshot extraction — that's doc-this-visor.
doc-this-visor
Use as an optional Discovery agent that documents the legacy system's UI from screenshots — without needing the system running. Extracts components (forms with field types/validations, tables with columns/actions/pagination, navigation menus and breadcrumbs), per-screen states (loading/empty/filled/error/confirm), navigation flow between screens, and writes one screens.md per unit plus globals (ui/inventory.md, ui/flow.md). Maps each screen to a unit per the project's [specs].granularity (module/use-case/endpoint/hybrid/feature/custom), creating empty unit folders ahead of Writer when needed (Writer respects existing folders). Triggers: '/doc-this-visor', 'document UI from screenshots', 'extract screens', dispatched by doc-this when the system has a UI and the user can supply screenshots. NOT for live UI scraping (use Playwright for that). NOT for design-token extraction (doc-this-design-system).
doc-this-writer
Fifth agent in the doc-this Discovery pipeline (generation). STRICTLY DESCRIPTIVE — turns accumulated cited evidence into folder-per-unit operational specs; never invents requirements. Specs are ATDD-ready: requirements.md catalogs every external surface the unit exposes, with Given/When/Then scenarios per public surface tagged @api/@browser/@cli/@message/@database and file:line cites. Binary 🟢/🔴 confidence; no 🟡. NFRs ONLY from a written non-functional contract — code patterns are NOT NFR evidence. Private endpoints get no @api (covered transitively via @browser). Generates code-spec-matrix.md from the manifest (row per source file); halts when a unit's UI page lacks read markup. Dispatched by doc-this after Architect+Detective — never auto-triggered by user phrasing; direct '/doc-this-writer' is for resume/debug in an active pipeline. NOT for SDLC promotion (doc-this-promote). NOT for review (doc-this-reviewer).
doc-this
Reverse-engineer a legacy codebase into ATDD-ready, traceable specifications. STRICTLY DESCRIPTIVE — documents what exists, never proposes or judges. Orchestrates Scout, Code Analyst, Detective, Architect, Writer, Reviewer plus optional Tracer, Visor, Data-Master, Design-System. Uses LSP for compiler-quality cross-file analysis when available, Understand-Anything graph as fallback. Classifies APIs public/private, catalogs HTTP/gRPC/CLI/message/UI/database surfaces, emits folder-per-unit specs with binary confidence (🟢 cited / 🔴 gap). Supports --incremental re-analysis via LSP blast-radius. Triggers: 'document this codebase', 'reverse engineer this system', 'extract requirements from legacy', '/doc-this'. NOT for docstrings. NOT for greenfield. NOT for proposing improvements, technical debt, or inventing NFRs. Delegates to doc-this-promote; the promoted specs feed whatever ATDD/TDD tooling the project already uses.
agent-cli
Use when building, designing, reviewing, or evaluating command-line tools for AI agent consumption -- structures commands with machine-readable JSON output on stdout, human diagnostics on stderr, adds --json/--fields/--dry-run/--quiet flags, implements semantic exit codes, enforces TTY-aware dual-mode output, hardens input against path traversal and injection, creates CONTEXT.md and AGENTS.md agent knowledge files, adds --help-json schema introspection, and scores CLI agent-friendliness on a 0-21 rubric across 7 axes. Triggers on: 'agent-friendly CLI', 'CLI for agents', 'build a CLI', 'design CLI commands', 'machine-readable output', '--help-json', 'CLI scoring', 'agent DX', 'context window discipline', 'evaluate CLI', 'CLI agent readiness', 'score this CLI'. NOT for TUI/full-screen apps. NOT for GUI apps. NOT for REST/GraphQL API design.
airflow-dags
Use when creating, debugging, or configuring Apache Airflow 3 DAGs — builds data pipelines with TaskFlow API or traditional operators, configures scheduling and asset-driven triggers, wires XCom data passing, sets up sensors and deferrable operators, generates dynamic task mappings, and structures multi-layer test suites. Triggers on DAG authoring, TaskFlow API, operators, sensors, scheduling, assets, dynamic tasks, XCom, or pipeline testing.
human-cli
Use when designing, building, reviewing, or evaluating command-line tools for human users -- structures commands with memorable naming and consistent grammar, adds interactive prompts with flag bypasses, implements color-coded output with spinners and progress bars, designs informative error messages with resolution URLs, enforces XDG config paths, adds shell completions and man pages, optimizes startup to under 500ms, implements TTY-aware dual-mode output, and scores CLI human-friendliness on a 0-21 rubric across 7 axes. Triggers on: 'CLI UX', 'human-friendly CLI', 'CLI design', 'CLI colors', 'CLI prompts', 'progress bar', 'CLI help text', 'error messages', 'CLI usability', 'design a CLI', 'evaluate CLI UX'. NOT for agent/machine CLI consumption (use agent-cli). NOT for TUI/full-screen apps. NOT for GUI apps.
okf-maintain
Use when adopting the Open Knowledge Format (OKF v0.2) in a repository, or maintaining a documentation bundle already in it: bootstraps a conformant tree, stamps and repairs YAML frontmatter, regenerates every index.md bottom-up so no document goes unlisted, excludes paths another tool owns via .okfignore, removes log.md and strips changelog/history sections because git already holds history losslessly, and wires CLAUDE.md/AGENTS.md/GEMINI.md to the root index so agents stop grepping for a document's identity. Ships a conformance check that fails closed, plus a coverage check that names every document no index reaches. Triggers on: 'set up OKF', 'make these docs OKF-conformant', 'regenerate the docs index', 'add frontmatter to the docs', 'which docs are missing from the index', 'our documentation keeps drifting'. NOT for writing a document's body or deciding its content - repo templates and the adr skill own that. NOT for reverse-engineering a codebase into fresh specs.
platform-sre-kubernetes
SRE-focused Kubernetes specialist for production deployments. Use when deploying to Kubernetes, reviewing manifests, or establishing reliability practices.
postmortem
Write a production-incident postmortem that reads well for humans and stays parseable by tooling. Produces docs/postmortems/YYYY-MM-DD-<slug>.md with machine-read YAML frontmatter (severity critical|high|medium|low), a stable H1 + filename date that together form a finding-id, and a numbered spine — executive summary, impact/blast radius with per-service evidence, timeline, root cause (mechanism + 5 whys + discarded hypotheses), empirical proof, detection, remediation (palliative vs root fix), action items, lessons learned, read-only appendices. Triggers: 'write a postmortem', 'post-incident review', 'incident record', 'document this outage', 'RCA document', or right after resolving/mitigating any production incident. NOT for reconciling a postmortem with the decision it contradicted. NOT for bug reports. NOT for live incident response.
prototype-spike
Use when a requirement or an unproven technique must be made clickable before it is built — produces a single self-contained HTML prototype that doubles as a design spike, whose control panel is the open questions. Rebuilds existing screens at high fidelity from real source (structure, copy strings, icons, tokens, each cited file:line; invents only what the requirement adds), derives one control per acceptance criterion or technical unknown, drives real data through a dev-server proxy that also proposes the route shape (live > capture > labeled stub, never invented), verifies every state in a real browser, and reports what the spike settled. Triggers on 'prototype FR-NNN', 'clickable prototype of FR-NNN', 'make this requirement clickable', 'spike this technique'. NOT for inventing UI from a prompt — use a generative-design skill. NOT for production frontend code. NOT the client-confirmation record — that is a spec-playback step. NOT an ADR writer.
requirements-elicitation
Systematic framework for analyzing product documents (PRDs, feature specs, user stories, roadmaps, one-pagers) to identify gaps, generate clarifying questions for PMs and engineers, and assess technical risks. This skill should be used when engineers or technical leads need to bridge PM documents and implementation by eliciting missing technical details rather than making assumptions. Use when asked to extract technical requirements, review specs, identify what's missing, or prepare clarifying questions from product documents.
create-review-plugin
Scaffold and author a custom Tessl reviewer plugin, by forking the default rubric or building one from scratch. Fetches the published default Tessl review rubric (tessl/default-skill-review) so you can read and tweak it, scaffolds the plugin directory, writes rubric files and config.json, and validates with tessl review run. Use when the user wants to create or customise a review plugin, fork or tweak the default reviewer rubric, change scoring weights, add custom judges, or build a domain-specific rubric for tessl review.
derive-review-rubrics
Derive custom review-plugin judges, rubrics, and scoring criteria from evidence — existing skills, PR review feedback, and accumulated agent logs — by finding where agents needed correction or skills failed to activate, then translating those patterns into scoring dimensions and anchors. Hands the rubric design to create-review-plugin for scaffolding. Use when the user wants a custom skill reviewer or scoring rubric grounded in how their agents actually behave — to grade skills consistently, or build review criteria from past PR feedback and agent logs.
skill-reviewer
Evaluate a SKILL.md for quality. An agent that dynamically discovers the rubric files and scores the skill against each, producing one result per rubric. Use when running a skill review workflow or testing skill quality against configurable rubrics.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.