User stories: Mike Cohn format + Gherkin acceptance criteria
Draft dev-ready user stories (As a / I want / So that) with Gherkin Given/When/Then criteria, anti-patterns and a template script
- What
- Draft dev-ready user stories (As a / I want / So that) with Gherkin Given/When/Then criteria, anti-patterns and a template script
- Cost
- Free
- Needs
- nothing to install — the skill is a writing methodology your agent follows; license of the source repo is not asserted, so read it yourself before reusing
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @deanpeters's component skill for writing dev-ready user stories: Mike Cohn's "As a / I want / So that" format paired with Gherkin acceptance criteria (Given/When/Then), with quality checks, five common pitfalls (technical tasks disguised as stories, generic "as a user", "so that" restating "I want to", multiple Whens, untestable Thens), worked good-vs-bad examples, and an optional CLI template script. Short listing: the repository declares NOASSERTION on its license, so the content is not reproduced here — follow the source link and judge it for yourself. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is a writing methodology your agent follows; license of the source repo is not asserted, so read it yourself before reusing Install "User stories: Mike Cohn format + Gherkin acceptance criteria" for me. It points my agent at @deanpeters's component skill for drafting dev-ready user stories — Mike Cohn format plus Gherkin acceptance criteria, with quality checks, pitfalls and a template script. Link-only listing: fetch it from the source, read it, and decide for yourself. Repository: https://github.com/deanpeters/product-manager-skills/blob/main/skills/user-story/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "user-story". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and remind me the source license is not asserted — I should read the repo before reusing its content. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.