Dev Story
- 1 installs
- 2 repo stars
- Updated April 18, 2026
- bkstock/casino-code-studios
dev-story is a Claude Code skill that runs a story from requirement parsing through technical design, implementation, self-test, code review, and a compliance gate.
About
dev-story is a Claude Code skill that runs an end-to-end story workflow: it reads a story's requirements, routes it to a domain specialist, does a brief technical design, implements, self-tests, auto-triggers code review, applies a compliance gate for payment/KYC/bonus work, and marks the story ready. A developer invokes it with a story id to take a single sprint item from requirements to review in one guided pass. The documentation is written in Japanese.
- Runs an eight-step story workflow from requirement parsing through implementation, self-test, and review
- Routes each story to a domain specialist agent and auto-triggers /code-review on changed files
- Adds a compliance gate that flags payment, KYC, or bonus stories for compliance review
Dev Story by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,980 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
dev-story capabilities & compatibility
- Capabilities
- story workflow · code review · project management
- Use cases
- project management · code review · testing
What dev-story says it does
ストーリー着手 — ストーリーの要件確認、技術設計、実装、テストの一連のワークフロー。
**Domain routing** — Assign to appropriate specialist agent
**Compliance gate** — If payment/KYC/bonus, flag for compliance review
npx skills add https://github.com/bkstock/casino-code-studios --skill dev-storyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 2 |
| Last updated | April 18, 2026 |
| Repository | bkstock/casino-code-studios ↗ |
What it does
Drive a single story from requirement parsing through implementation, self-test, code review, and a compliance gate.
Who is it for?
Developers working sprint stories that may touch payment, KYC, or bonus logic.
Skip if: Ad hoc code edits that are not tracked as a story.
When should I use this skill?
Starting work on a story by its id and wanting the full requirements-to-review workflow.
What you get
A story is implemented, self-tested, code-reviewed, compliance-gated where needed, and marked ready in the sprint file.
- implemented and self-tested story
- code review on changed files
- compliance flag for payment/KYC/bonus stories
By the numbers
- 8-step story workflow
Files
Dev Story Workflow
1. Read story — Parse requirements and acceptance criteria 2. Domain routing — Assign to appropriate specialist agent 3. Technical design — Brief design before coding 4. Implementation — Code with domain-specific rules enforced 5. Self-test — Run relevant tests 6. Code review — Auto-trigger /code-review on changed files 7. Compliance gate — If payment/KYC/bonus, flag for compliance review 8. Mark ready — Update sprint file
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669FAQ
What triggers the compliance gate?
If the story touches payment, KYC, or bonus logic, it is flagged for compliance review.
Does dev-story review its own code?
Yes, it auto-triggers /code-review on the changed files after implementation and self-test.