AGENT SKILLS · MISSION KIT / windyd

windyd · Agent Skills

21 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

windyd
Community

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".

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

resolving-merge-conflicts

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

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

to-tickets

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

triage

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

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

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.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

writing-great-skills

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

installs
2
GitHub stars
0
Updated
Jul 31
windyd
Community

ask-matt

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

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

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.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

domain-modeling

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

handoff

Compact the current conversation into a handoff document for another agent to pick up.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

implement-spec

Implement the result of /to-spec and /to-tickets in code.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

improve-codebase-architecture

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

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

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.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

retro

Conduct a retrospective on a coding session.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

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.

installs
1
GitHub stars
0
Updated
Oct 11
windyd
Community

teach

Teach the user a new skill or concept, within this workspace.

installs
1
GitHub stars
0
Updated
Oct 11