wsagency

ws-ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

ws-improve-codebase-architecture

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

ws-setup-matt-pocock-skills

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Testing & QA Listed

ws-to-spec

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

ws-triage

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

ws-wayfinder

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Testing & QA Listed

ws-implement

Implement a piece of work based on a spec or set of tickets.

ws-grill-with-docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

ticket-writing

How to turn a brief task description into a well-structured Jira ticket (summary, user story, Given/When/Then acceptance criteria, codebase research). Use when writing or enhancing a Jira ticket, user story, or acceptance criteria, or when asked to "enhance" a task description.

ws-jira-conventions

WS Agency Jira commit/branch/PR conventions. Use when working with Jira tickets, writing commits that reference issue keys (e.g. WSC-123), naming branches, or composing PR titles. Documents the project's Conventional Commits + Jira suffix format and Smart Commit syntax.

project-hub-conventions

Conventions for WS Agency multi-repo project hubs (subfolder layout, project.yaml schema, context-file cascade, .gitignore managed block, invoke-ai.sh contract). Use when creating, extending, or troubleshooting a `<project>-main` hub repo, or when asked about "project hub", "multi-repo", or `<name>-main` repos.

ws-code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

ws-codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

ws-diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

ws-domain-modeling

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

ws-graph-engineering

Graph-engineering methodology behind the ws-matt skill set — the node/edge/state contract, dynamic fan-out and fan-in, the file-handoff protocol, and per-harness execution notes (Claude Code, omp, Codex). Use when asked about "graph engineering", an "agent graph" or "skill graph", "fan-out" of workers, or how to "orchestrate subagents" across the ws-matt nodes.

ws-prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Testing & QA Listed

ws-tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

ws-artefacts-explained

Contract for a hub's `role: explained` repo — generated, self-contained HTML product documentation consumed by the ws-artefacts platform (artefacts.wsagency.io). Use when generating or refreshing product-explained artefacts, when asked about an "explained repo" or "ws-artefacts", or about the artefact HTML / meta.json format.

ws-grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

ws-research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

ws-resolving-merge-conflicts

Use when you need to resolve an in-progress git merge/rebase conflict.

adr

Knowledge about Architecture Decision Records (ADRs) using MADR v4.0.0 format

conventional-commits

Knowledge about Conventional Commits standard for structured, meaningful commit messages

diataxis

Knowledge about the Diátaxis documentation framework for creating effective technical documentation

dual-track-docs

Convention for splitting documentation into user-facing (docs/) and internal contributor (dev-docs/) tracks. Use when scaffolding documentation, deciding where a new doc belongs, or migrating an existing single-track docs layout.