ihudak

by Daniel Ziegenberg

Atlassian CLI (acli) reference skill for Jira and Confluence: JQL search, work items, comments, links, attachments, watchers, projects, sprints, boards, filters, and Confluence spaces, pages and blog posts. Adds container-friendly authentication (token on stdin; --web OAuth cannot complete without a browser) and a write policy in which --yes carries the user's approval, given in the conversation first, and a blast-radius count precedes any --jql/--filter mutation. Requires the acli binary on PATH.

by Ivan Gudak

Five slash commands for the implementation half of the product lifecycle: `/design` turns a specification into a design, with Opus review and an optional three-take fan-out on a contested interface. `/implement` builds it, gated by Opus plan critique and code review before tests. `/ready` verifies an ARD/spec/design chain's readiness, read-only, no tracker read. `/upgrade` plans and executes dependency upgrades; `/vuln` researches and fixes a CVE. Twelve subagents, one hook, fifteen reference files, no bundled skill. Every code-changing command commits before the run ends; push and PR sit behind one consent choice. Depends on the companion `workflows-core` plugin for its shared foundation. The product-definition ladder, `/epics`, and the BRD-to-PRD route now ship in `product-workflows`; documentation commands ship in `docs-workflows`. Neither is a dependency.

by Ivan Gudak

Commands for a product's documentation and release notes. /docs-init scaffolds a documentation repository from nothing: a Material for MkDocs skeleton, public and internal builds over one content root, Vale, CI and a docs-profile.yml. /docs-brand extracts a logo and colour pair from the product's code and applies them, WCAG contrast-checked. /docs-serve runs the site's dev server. /docs-audit turns the product's own code and specs tree into a coverage grid and a prioritised backlog of the pages it is missing, behind an Opus review gate. /document edits prose directly, or keyed to a PRD folder writes product docs from its implementation diffs behind an Opus review gate. /docs-profile refreshes a docs repository's machine-readable profile; /release-notes drafts a destination-shaped entry from the same folder. Depends on workflows-core and prose-style.

by Fixture

Second fixture plugin. Exists so the gate's plugin loop is exercised by more than one element.

by Ivan Gudak

Reviews an OpenAPI specification against bundled REST API and IAM permission-naming guidance, and reviews application code or UI against bundled public design-system and accessibility standards. Ships the guidance it reviews against — Google AIP, Zalando, Microsoft REST, OpenAPI 3.1 and ~20 RFCs for APIs; Apple HIG, Material Design 3, Microsoft Fluent 2, W3C WCAG 2.2, ARIA APG and NN/g for interfaces — plus a Spectral ruleset that runs against a spec directly. Standalone: it consumes no workflow artefact and produces none.

by Ivan Gudak

LLM Wiki pattern for an active Obsidian vault. Ten slash commands (/wiki-init, /wiki-ingest, /wiki-scan, /wiki-query, /wiki-save, /wiki-lint, /wiki-hot, /wiki-tags-refresh, /wiki-task, /wiki-tasks-extract) compile knowledge from meetings, projects, daily notes, and raw sources into a persistent, cross-referenced wiki at wiki/, with integrated task management via Obsidian Tasks. Supports Claude Code and GitHub Copilot as first-class agents with session-continuity hooks.

by Ivan Gudak

Fourteen slash commands for defining a product — its requirements, architecture and specification: a six-command BRD-to-PRD route (/brd-intake → /brd-split → /prd-ground → /brd-split → /brd-interview → /brd-package → /brd-reconcile) that grounds a customer's requirements document, settles it with them, and seeds the PRD, ARD and specification; the idea→PRD→ARD→specification ladder (/idea → /create-prd → /update-prd → /create-ard → /specify), with /prd-ground optionally grounding the PRD itself; /epics, deriving Epics from a PRD; and /prd-proposal and /brd-proposal, pricing a graded requirement set in human hours — never money — with every cost driver citing a record on disk and gating nothing. Fourteen agents carry the grounding, figure transcription, reconciliation, review and Epic writing. Twelve reference pages define the artifact formats and the link walk these commands share.

by Ivan Gudak

Pluggable prose style checker and writing aid for documentation, planning documents, and release notes. Ships a vendor-neutral baseline — terminology, word list, voice and tone, grammar, formatting, UI interactions, inclusive language, and prose accessibility — distilled from the Microsoft, Google, and Apple style guides, Chicago, the Conscious Style Guide, and WCAG. Point it at your own organization's style guide and the overlay augments or overrides that baseline; every resolution miss falls back silently. Provides /prose-review-pr, /prose-review-docs (with --fix), /prose-style-refresh, a prose-style-checker agent, a prose-fixer agent, and a prose-style-rules skill.

by Fixture

Third fixture plugin. Ships a command, has no docs/ tree, and declares a name its DIRECTORY does not carry -- so it pins two things nothing else here does: that check 4's manifest assertion walks plugins outside PLUGIN_RELS, and that a namespace is the declared name rather than the directory.

by Ivan Gudak

Shared foundation for the dev-workflows plugin family: the addressing grammar and specs-repo git entry points, phase handoff, model routing, escalation and finding-triage rules, cost/feedback/follow-up emission, and the reference loader skill that lets a dependent plugin read them. Also carries the family-meta utility commands — /feedback, /prompt, /prompt-brainstorm, /prompt-grill-me, /statusline — and /frames for indexing design frame sets.