pavel-rp/wf-plugin

wf:* skill chain: spec/plan/implement, verify, QA (gen/run/auto/followup), classify, triage, branch/commit/pr. Domain-free, tracker-agnostic core — tracker/delivery integrations register via capability packs (wf-ado, wf-git, ...). Stack/domain capabilities (browser-qa, angular test-host, node-ts) each ship in their own plugin.

wf tracker-provider pack: the ado capability owning the wf capability-registry's tracker surface (Azure DevOps work-item get/create/update/list-children/comment/status bindings and status/milestone/cycle queries, plus the AB#<id> PR-link autolink). Ships /wf-ado:init for one-command self-registration.

wf Angular stack pack: the angular capability owning the wf capability-registry's qa-execution host surface. Ships /wf-angular:qa-host (routed Angular test-host scaffolder + ephemeral backend-controller analog) and /wf-angular:test-page (browser-run black-box DI-level test harness). Every project-specific token in the scaffolded output is profile-slot-driven, so scaffolding a differently-named app emits no borrowed identifiers; surface: host composes with browser-qa's surface: engine with no partition collision. Tracker-agnostic (requires: git only). Ships /wf-angular:init for one-command self-registration.

wf audit pack: the audit capability (five domain-free adversarial verify lenses plus an optional composite retrospective report) co-located with the sr capability (a lightweight pre-commit adversarial self-review lens reusing the audit correctness rubric intra-plugin). Dependency-free (no requires) — composes in bare-core mode. Ships /wf-audit:init for one-command self-registration of both capabilities.

wf authoring toolkit: the author-caps capability, teaching how to author capabilities, skills, and plugins for this marketplace. Ships two model-invoked reference skills — /wf-author-caps:authoring-guide (core-versus-capability sorting, plugin anatomy, interface-first skill design, skill-versus-subagent, native and registry composition, the registration flow, canonical vocabulary) and /wf-author-caps:authoring-taxonomy (the SDD phase spine, the contribution kinds, aggregate-versus-partition policy, manifest schema v2, the registry row, constitution composition, registry validation) — that load by description auto-selection when an authoring question comes up, no slash command required. Declared kind: both; attaches five inline phase fragments — guidance at spec and implement, two findings at verify (structural validation and reference existence), a scenario at qa-generation — plus constitution article keys, all inert until registered. Ships four scaffolders that emit real, already-linted files — /wf-author-caps:new-skill, /wf-author-caps:new-capability, /wf-author-caps:new-pack (a complete registerable pack skeleton: plugin manifest, capability folder, and an init skill on the pack-onboarding spine) and /wf-author-caps:new-provider (a capability bound to one contract surface, speaking only the abstract operations with binding values in profile slots) — plus /wf-author-caps:init for one-command self-registration.

wf browser-QA feature pack: the browser-qa capability owning the wf capability-registry's qa-execution engine surface. Ships /wf-browser-qa:qa-engine, a stack-agnostic in-thread browser-automation QA engine that drives any web app, reaches browser-level preconditions, captures console/network, screenshots on FAIL, and emits per-scenario verdict blocks; core's /wf:qa-auto dispatches the per-scenario browser drive to it. Tracker-agnostic (requires: git only). Ships /wf-browser-qa:init for one-command self-registration.

wf core-authoring pack: the core-authoring capability, carrying the knowledge for authoring the wf core plugin itself — the domain-free skill spine, the frozen contracts under the core plugin's _contracts folder, and the repository authoring rules its CI gates enforce. Declared kind: both; it ships its own skills and is authored to attach phase fragments. Its first contribution is the distilled authoring-vocabulary article it declares as constitution articles, so a session in this repository starts with those rules in its injected context; it also carries the craft-C4 authoring lint its own fixtures runner gates in CI, and it fills the new-skill.constraints composition point declared by /wf-author-caps:new-skill with this repository's core-only authoring rules, so a skill scaffolded here is core-compliant as it is emitted. Ships /wf-core-authoring:init for one-command self-registration of the capability, /wf-core-authoring:new-contract to scaffold a core contract pair that is green under the repository's contract-shape guard on its first run, /wf-core-authoring:add-term to land one authoring-glossary term together with the parse-contract entry that makes it enforceable, and /wf-core-authoring:preview-edit to see what a pending, uncommitted capability-manifest, registry, or taxonomy-contract edit would do before it reaches a commit.

wf hermetic fixture-provider pack: the fake capability owning BOTH the wf capability-registry's delivery AND tracker surfaces with an in-memory, scripted, op-recording binding. Every abstract delivery/tracker op returns a scripted response from a fixture-local scripts file and appends its invocation to a machine-readable op log; no network, git, gh, or tracker MCP is ever reached (a static no-egress self-check enforces it). Registered only inside fixture registries as the sole owner of both surfaces (real-project co-registration correctly trips the overlap validation). The C016 skill-eval test seam. Ships /wf-fake:init for one-command self-registration.

wf delivery-provider pack: the git capability owning the wf capability-registry's delivery surface (branch/commit/push/PR git+gh bindings). Ships /wf-git:init for one-command self-registration.

wf generic host-provider pack: the host capability owns only the wf capability-registry's qa-execution host surface. Ships /wf-host:qa-host for profile-driven, temporary API exposure, host augmentation, transactional persistence seed, synthetic fixtures, health verification, and durable reverse-order teardown recovery backed by a run-scoped ledger. Stack- and tracker-agnostic. Ships /wf-host:init for resolver-owned one-command self-registration.

wf tracker-provider pack: the linear capability owning the wf capability-registry's tracker surface (Linear issue get/create/update/list-children/comment/status/attachment bindings and status/milestone/cycle queries via mcp__claude_ai_Linear__* tools). A second, independent binding of the tracker contract alongside wf-ado. Ships /wf-linear:init for one-command self-registration.

wf Node/TypeScript stack pack: the node-ts capability owning a dependency-free unit-test harness for pure TS helpers (parsers, formatters, coercion helpers) that need no Angular runtime. Ships /wf-node-ts:test-node; the implement phase aggregates its test-authoring guidance when registered. Tracker-agnostic (requires: git only). Ships /wf-node-ts:init for one-command self-registration.

wf PR-review feature pack: the pr-review feature capability shipping the user-invoked /wf-review:address-pr and /wf-review:review-pr skills. Reads/verifies/addresses review comments and CI failures and posts verified findings entirely through the delivery provider's PR-interaction operations (pr-comments-read/pr-comment-post/checks-read/review-thread-resolve), treating review-tool output as hypothesis. Composes natively on install for its two skills; ships /wf-review:init for one-command self-registration of the pr-review capability ahead of its first contribution fragment.

wf skill-eval harness pack: the sandbox-testing feature capability. Runs real headless wf:* skill invocations hermetically in a fingerprinted container (runner/), judges the runner's structural outputs — terminal block, workspace file set, invoked contract-op set — statistically over N runs and emits a variance-aware report separating drift from regression (assert/), ships the SMOKE/STATISTICAL tier commands and the baseline-comparison primitive, the behavioral-regression corpus mined retrofit-first from observed failures (corpus/), and the findings-loop procedure that turns a new observed failure into an assertion. Owns no provider surface and attaches no phase fragment; downstream fixtures that script a provider pair with the wf-fake pack (enforced loudly at run time, not via requires:). Ships /wf-sandbox-testing:new-experiment, an interview-driven scaffolder that emits a runnable experiment kit — manifest, kit-root files, and an engine-derived runbook — for the shared experiment engine, plus /wf-sandbox-testing:init for one-command self-registration.