story-check
Skill0 starsChanged 3 months agoMITView on GitHub
Compare a GitHub issue or story with the current repository implementation and report scope discrepancies. Use when a GitHub issue link is provided and the user wants to verify that implementation matches the declared story.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bybren-llc/story-systems-templatetheir own version, first seen Aug 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- bybren-llc/story-systems-template★ 66same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend-doc-syncSkill
- check-documentation-gapsSkill
- check-test-gapsSkill
- commiterSkill
- docs-guardianSkill
- monthly-doc-actualizerSkill
- release-note-writerSkill
- story-guardianSkill
- story-updateSkill
- tech-debtSkill
- test-scenario-guardianSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Verify that the current repository implementation matches the scope declared in a GitHub issue or story.
- Distinctive: line 14
Use this skill when:
- Distinctive: line 24
Read the issue through the GitHub MCP tools first, as required by repository instructions.
- Distinctive: line 25
Use the issue title, body, acceptance criteria, and explicitly linked requirements as the declared scope.
- Distinctive: line 26
Treat comments, labels, and linked pull requests as supporting context only.
- Distinctive: line 27
If the issue cannot be read, report the exact access or retrieval error and stop before making scope claims.
- Distinctive: line 31
Check the working-tree status and relevant diff so uncommitted work is included in the review.
- Distinctive: line 33
Follow code paths far enough to verify behavior, not just the presence of a filename or symbol.
- Distinctive: line 34
Use tests and test scenarios as evidence, but do not treat a passing test alone as proof that the full story is implemented.
- Distinctive: line 50
Always print a concise comparison summary.
- Distinctive: line 57
If no discrepancies are found, state that the implementation is scope-aligned and identify the evidence reviewed.
- Distinctive: line 81
Do not create commits, alter files, post GitHub comments, or change issue state as part of this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Story Check
Purpose
Verify that the current repository implementation matches the scope declared in a GitHub issue or story. This is a read-only review: do not modify GitHub resources or implementation files unless the user separately requests a fix.
When To Use
Use this skill when:
- The user provides a GitHub issue URL or asks to check implementation against an issue.
- The user asks whether delivered work matches a story, acceptance criteria, or declared scope.
- The user asks for out-of-scope or missing implementation findings.
Required Workflow
1. Resolve the declared scope
- Extract the GitHub owner, repository, and issue number from the link.
- Read the issue through the GitHub MCP tools first, as required by repository instructions.
- Use the issue title, body, acceptance criteria, and explicitly linked requirements as the declared scope.
- Treat comments, labels, and linked pull requests as supporting context only; do not silently promote them to requirements.
- If the issue cannot be read, report the exact access or retrieval error and stop before making scope claims.
2. Inspect the current implementation
- Check the working-tree status and relevant diff so uncommitted work is included in the review.
- Inspect the implementation files, tests, migrations, configuration, and documentation relevant to each requirement.
- Follow code paths far enough to verify behavior, not just the presence of a filename or symbol.
- Use tests and test scenarios as evidence, but do not treat a passing test alone as proof that the full story is implemented.
- Record precise evidence using repository-relative file paths and line numbers where available.
3. Compare scope to implementation
Classify every meaningful requirement as one of:
- Implemented — current behavior and supporting evidence satisfy the requirement.
- Partially implemented — some required behavior exists, but a stated condition, edge case, or acceptance criterion is missing.
- Missing — no sufficient implementation evidence was found.
- Out of scope — implementation adds behavior or files not supported by the declared issue scope.
- Ambiguous — the story is not specific enough to determine compliance; state the exact ambiguity.
Distinguish functional scope from incidental implementation details. Do not report normal refactoring, required tests, or documentation synchronization as out of scope unless they introduce user-visible behavior not justified by the story.
4. Report discrepancies
Always print a concise comparison summary. If discrepancies exist, list each one with:
- Classification
- Requirement or story excerpt paraphrase
- Implementation evidence or missing evidence
- Impact or risk
- A focused follow-up recommendation
If no discrepancies are found, state that the implementation is scope-aligned and identify the evidence reviewed. Do not claim certainty when the issue or implementation could not be fully inspected.
Output Format
Use this structure:
Scope: <issue URL and title>
Implementation examined: <branch/working-tree context and key areas>
Overall status: Scope-aligned | Discrepancies found | Blocked | Ambiguous
Requirement comparison:
- <requirement>: Implemented | Partially implemented | Missing | Out of scope | Ambiguous
Discrepancies:
1. [<classification>] <short finding>
Evidence: <issue requirement and repository evidence, or missing evidence>
Impact: <why it matters>
Follow-up: <focused recommendation>
Verification limits:
- <only material limitations; write “None” when applicable>Do not create commits, alter files, post GitHub comments, or change issue state as part of this skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

