jrey-skills

Plugin jrey-skills from marketplace jrey8343 in jrey8343/skills. Commands read from the repo's manifest — 8 days ago.

Skills (14)

• deciders

  Write event-sourced domain logic as Deciders: pure decide(command, state) → events and evolve(state, event) → state functions with an initial state, tested given events / when command / then events, and met by a thin shell that loads, appends and projects. Use when writing or changing event-sourced

• event-storming

  Run a facilitated event-storming session with the user, from domain events on a timeline to bounded contexts, glossary terms and candidate Deciders, written into a storm doc in the repo.

• discover-domain

  Infer what this product is, who it serves and what they come to do from the code, grill you on the gaps, then write PRODUCT.md, avatars, journeys and a seed glossary.

• persona-review

  Walk a feature, journey or spec as each avatar it serves, through the code and copy or as a live click-through, and log where it confuses them, dead-ends, or isn't worth their time.

• product-modeling

  Build and sharpen a product's model of itself: PRODUCT.md (vision, principles, non-goals, metrics), avatars (the people it serves) and journeys (what they come to do). Use when discussing product direction, personas, avatars or user journeys, when editing PRODUCT.md, avatars or journey files, when l

• product-review

  Product designer and manager verdict (build, build-with-changes, rethink, don't-build) on a spec, issue, PR, branch or shipped feature, judged against PRODUCT.md, the avatars and their journeys.

• project-docs

  Formats and drift rules for a project's three kinds of docs: feature docs, user docs and agent docs (CLAUDE.md, AGENTS.md), with verified-at SHAs for drift. Use when writing or updating docs for a feature or journey, when a change alters documented behaviour, when slimming or restructuring CLAUDE.md

• docs-audit

  Check agent docs, ADRs, feature docs and user docs against the code and the journeys: missing pages, drifted pages, dead paths and broken links, then file them for Triage.

• perf-audit

  Audit performance against explicit budgets (round trips, rows read, payload and bundle size, latency) using code, napkin math and production signals, then file what breaks budget.

• prune-docs

  Clean up agent-facing docs. Slim CLAUDE.md / AGENTS.md to an index, move history and how-it-works into feature docs and ADRs, delete stale facts and dead references.

• report-findings

  Publish audit findings to the issue tracker: fingerprint dedupe against existing issues, one tracking issue per sweep, capped child issues labelled for Triage (never with a state label, never as a PR). Also defines headless vs interactive audit modes, the docs/agents/audits.md dependency, incrementa

• schedule-audits

  Set this repo up to run the audit skills on a schedule in its own GitHub Actions: seed docs/agents/audits.md, render .github/workflows/audits.yml from it, and walk the 1Password and GitHub token setup.

• security-audit

  Audit the whole repo for security risks (tenant isolation, authorisation, secrets, input handling, headers, dependencies, AI features) and file ranked findings.

• test-audit

  Find journeys and risky modules that lack the tests they need, then file prioritised gaps.

Similar plugins