yokeloop

Turns the current conversation and codebase understanding into a PRD, publishes it as a GitHub issue, and saves a local copy in docs/ai. Does not interview — synthesizes what is already known. Activates when the user writes "prd", "create a prd", "write a prd", "turn this into a prd", "product requirements doc", "draft requirements".

Shows development status in the repository: branch, uncommitted changes, recent commits, diff vs main, hot files, semantic summary. Used when a developer writes "status", "gst", "git status", "what's going on", "repo state", "show changes".

Codebase exploration and brainstorming. Activates when the user writes "explore", "explain", "compare", "what if", "brainstorm", "investigate", "figure out", "analyze", "how is it built", "how does it work", "tell me about", "why", "what are the options", "suggest an approach", "show the architecture".

Executes a task per plan. Triggered when the user writes "execute", "do", "run the plan", "implement", or passes a path to a plan file and asks to execute it.

Docs-aware grilling: interrogates the user's plan one question at a time AND maintains the domain glossary (CONTEXT.md) and architecture decision records (docs/adr/) inline as decisions crystallise. Used to stress-test a plan against the project's language and documented decisions; for a plain interview that writes no files, use grill. Activates when the user writes "grill-docs", "grill with docs"

Prepares a project for the yoke flow — stack detection, generation of CLAUDE.md and yoke-context.md. Used when the user writes "bootstrap", "set up yoke", "prepare the project", "yoke init", "setup yoke", "first run", "connect yoke", "create CLAUDE.md".

Regenerates the public skill catalog from `skills/*/SKILL.md` — per-skill MDX pages under `site/src/content/docs/skills/`, the table between `<!-- yoke:skills:start -->` markers in `README.md`, and the bullet list between the same markers in `CLAUDE.md`. Activates when the user writes "sync docs", "regenerate docs", "update the skill catalog", "rebuild docs", "refresh the catalog", or passes `--ch

Skill factory for the yoke plugin. Full pipeline for creating a new skill: task analysis, design with a mermaid diagram, implementation of SKILL.md and agents, quality validation, documentation creation, updating README and CLAUDE.md. Used when the user writes "create a skill", "new skill", "add a skill", "make a skill", "skill for".

Publishing the yoke plugin: quality checks, documentation validation, version bump, tag, push, GitHub release. Used when the user writes "release", "publish", "ship version", "make a release", "prepare a release", "new version".

Quick fix or follow-up change. Used when the user writes "fix", "patch", "correct", "tweak", "polish", "small fix", "quick fix", or describes a small change after /do.

Breaks a plan, spec, or PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets), publishes them in dependency order, and saves a local index in docs/ai. Activates when the user writes "issues", "break into issues", "create tickets", "split into tasks", "decompose into issues", "make implementation tickets", "tracer bullets".

Finds problems in code, fixes them and produces a report. Used when the user writes "review", "code review", "find issues", "find bugs", "check code", "code analysis", "prepare a report", "what's wrong with the code", or after /do to analyze changes.