Review a story markdown against a story tracker SKILL.md skillA

Review a story markdown against a story tracker from intai/story-flow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add intai/story-flow/Review a story markdown against a story tracker@git:20261002.c0ba224

Pins git:20261002.c0ba224 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
intai/story-flow
Path
plugins/story-flow/skills/review-story-against-ticket/SKILL.md
Versions recorded
8
Latest version
git:20261002.c0ba224, committed Oct 2, 2026
First version recorded
Aug 19, 2026
Size
6,501 bytes
Repository stars
16
License
MIT

Review story.md requirements and tasks, optionally against a story from the story tracker.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Review a story markdown against a story tracker

## Instructions

- When no ticket ID is given, skip to reading the local story markdown and review it without story tracker comparison.
- Fetch the story by its ticket ID (e.g. PROJ-123, 86d2uf1mh, 4821, AB#4821) using the project's story tracker MCP tools (Jira, ClickUp, Azure DevOps), to retrieve the complete story details including type, description, acceptance criteria, subtasks and Figma links (any `figma.com` URL, searching the ticket's comments, custom fields and attachments as well as its description), and download its attachments. If no story tracker MCP tool is available, tell the developer the project has no story tracker MCP server configured (`/mcp` to check status) and ask them to paste the story details or drop the ticket argument — never guess at the story content.
- Treat the ticket as a bug when its type is `Bug`, `Defect`, `Incident` or equivalent, or when it carries steps to reproduce with actual and expected behaviour.
- For a bug ticket, also extract the steps to reproduce, and the actual and expected behaviour. Review the downloaded attachments for details the description omits.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add intai/story-flow/Review a story markdown against a story tracker@sha256:253e4a97c93883a3

The line at the top of this page pins the label git:20261002.c0ba224, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_dwoijnkaalv4tk6y.svg)](https://markdownregistry.com/a/art_dwoijnkaalv4tk6y)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 8 versions of this file, between Aug 19, 2026 and Oct 2, 2026, about one every 6 days.

versioncommittedcommitsizeaudit
git:20261002.c0ba224 latest2026-10-02 c0ba224 6,501 BA view · diff
git:20260925.f521e422026-09-25 f521e42 6,132 BA view · diff
git:20260918.1f28c342026-09-18 1f28c34 5,676 BA view · diff
git:20260917.d6b24352026-09-17 d6b2435 5,200 BA view · diff
git:20260915.05d491e2026-09-15 05d491e 5,227 BA view · diff
git:20260914.fa75c792026-09-14 fa75c79 5,210 BA view · diff
git:20260820.53a5fe52026-08-20 53a5fe5 4,950 BA view · diff
git:20260819.ce66d462026-08-19 ce66d46 4,773 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6501 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

intai/story-flow · 16 stars · license MIT · pushed 2026-11-04 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_dwoijnkaalv4tk6y
GET https://markdownregistry.com/api/v1/resolve?ref=intai/story-flow/Review a story markdown against a story tracker
GET https://markdownregistry.com/api/v1/blob/253e4a97c93883a38b74ef7d9bb11683946cc919264cb4f95ffce4cc2bdf3eac

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from intai/story-flow

Learn what defines effective BDD scenarios SKILL.md skill
intai/story-flow · plugins/junior-flow/skills/learn-bdd-scenarios/SKILL.md · Interactive guidance on writing complete, effective BDD scenarios for story-flow.
git:20260813.f0239bc · audit A · 16 stars
Learn why to review implementation even with 100% test coverage SKILL.md skill
intai/story-flow · plugins/junior-flow/skills/learn-review-implementation/SKILL.md · Interactive guidance on why human code review is essential for readability and maintainability.
git:20260216.ed289a5 · audit A · 16 stars
Learn why to discuss technical design before implementation SKILL.md skill
intai/story-flow · plugins/junior-flow/skills/learn-technical-design/SKILL.md · Interactive guidance on creating technical design PRs to align with your team before coding.
git:20260811.7c0af34 · audit A · 16 stars
Analyze task dependencies for parallel execution SKILL.md skill
intai/story-flow · plugins/story-flow/skills/analyze-task-dependencies/SKILL.md · Parse story markdown to identify task dependencies and parallel execution opportunities.
git:20260910.adf7c27 · audit A · 16 stars
Draft a story markdown from a story tracker or feature description SKILL.md skill
intai/story-flow · plugins/story-flow/skills/draft-story-markdown/SKILL.md · Generate a draft story markdown by analyzing a story tracker or feature description, Figma designs, and the codebase.
git:20261014.3af5928 · audit A · 16 stars
Execute BDD scenarios SKILL.md skill
intai/story-flow · plugins/story-flow/skills/execute-bdd-scenario/SKILL.md · Execute BDD test scenarios from .feature files using browser automation.
git:20261104.ffce5b2 · audit A · 16 stars
Implement a story according to the requirements and tasks SKILL.md skill
intai/story-flow · plugins/story-flow/skills/implement-story-markdown/SKILL.md · Implement story.md requirements and tasks.
git:20261003.f640913 · audit A · 16 stars
Plan BDD scenarios SKILL.md skill
intai/story-flow · plugins/story-flow/skills/plan-bdd-scenarios/SKILL.md · Plan BDD scenarios.
git:20261016.7c93170 · audit A · 16 stars
Prepare implementation review comments on a pull request SKILL.md skill
intai/story-flow · plugins/story-flow/skills/prepare-implementation-review-comments/SKILL.md · Post reviewer-facing evidence on a pull request - reading order, requirement traceability, risks, discussion points…
git:20261029.3a24c1b · audit A · 16 stars

Every file in intai/story-flow

Browse by kind, by grade A, or by owner.