story-skills

Use when you want to pick up and fully ship a Shortcut *bug* story end-to-end, where you first validate the root cause against real data before planning a fix. Typically via a `bug-story <story-id>` command. Triggers on a defect, regression, broken behavior, or incident to fix — not a new feature.

Use when you want to prepare a sprint review demo: collect the stories one person finished in a given sprint that actually landed in this repo, cluster them into a few recognizable topics, and build a single demo page (one route + controller on a throwaway demo branch) that shows every screen in iframes so nothing has to be clicked together live. Typically via a `create-demo <sprint> <gebruiker>` command. Triggers on "demo voor de sprint review", "laat zien wat we deze sprint gedaan hebben".

Use when you want to quickly create a Shortcut story from a one-line intent — short title, a description of at most three sentences, and the team fields already filled in. Typically via a `create-story <wat er moet gebeuren>` command. Triggers on "maak een story", "zet dit in Shortcut" or dictating a task that should land on the board.

Use when you want to pick up and fully ship a Shortcut *feature* story end-to-end (build new functionality), typically via a `feature-story <story-id>` command. Triggers on a new feature, enhancement, or user story to implement — not a bug fix.

Use when you want to pick up a Shortcut *feedback* story — a request, remark or wish from a user, customer, PO or support — where you first check whether it fits a small scope before building anything, and may conclude that no code change is needed. Typically via a `feedback-story <story-id>` command. Triggers on user feedback, a small change request or a remark to follow up — not a planned feature and not a defect.

Use when you want to patch a repository for security updates — read its open Dependabot alerts, pick the lowest safe target version per package, bump it, verify, and open one PR per package. Typically via a `patch-repo [owner/repo …] [--auto]` command. Triggers on security patching, vulnerability alerts, CVE/GHSA follow-up or dependency bumps for security.

Use when you want to review feedback on the pull request for a Shortcut story together, one comment at a time, before changing code or replying on GitHub. Typically via a `pull-request-feedback <story-id>` command. Triggers on PR feedback, review comments, Greptile comments, or deciding what to do with review suggestions.

Use when you want to understand how something in this codebase actually works and want that explained in plain language, typically via a `uitleg <onderwerp>` command. Researches the current repo plus sibling repos one directory up (read-only, including git history) and writes a lasting explanation note to `Codebase/` in Obsidian. Triggers on "leg uit hoe X werkt", "hoe zit X in elkaar", "zoek uit waarom X zo is". Not for implementing changes.