菜单
Convert a feature request into a user story, save it, implement it via ship-it, and validate with acceptance tests. Use when user says "new user story", "implement this story", "story to ship", or describes a feature they want built as a user story.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Kill all running local development processes (TanStack Start dev, email service, PostgREST), wait for termination, then restart them. Use when user says "boot local", "restart local", "reboot dev", or needs to refresh local services.
Run user story acceptance tests using Playwright browser automation. Executes test steps from user-stories/*.md files and reports pass/fail status with reasons. Use when user says "run user stories", "test user stories", "acceptance test", or "run e2e tests".
Scrape, load, and manage the base recipe pool for the meal planner. Handles scraping Swedish recipe sites, loading into database, and verifying integration. Use when user says "scrape recipes", "load base recipes", "base recipe pool", or "update base recipes".
Evaluate test coverage and create appropriate tests based on risk assessment. Use when user says "build tests", "update tests", "add test coverage", "write tests for this", or "improve test coverage".
Reviews code quality, pattern adherence, and architecture with red-team validation. Use when user says "check your code", "code quality review", "is this well-written", or "review code quality". Different from check-your-work which finds bugs.
Orchestrates 6 quality agents in parallel (duplicate-detector, user-intent, deep-bug-hunter, security, performance, correctness) with severity validation. Use when user says "check your work", "review what we wrote", "quality check", or after writing new features.
| name | story-to-ship |
| version | 1.0.0 |
| description | Convert a feature request into a user story, save it, implement it via ship-it, and validate with acceptance tests. Use when user says "new user story", "implement this story", "story to ship", or describes a feature they want built as a user story. |
| allowed-tools | Task, TaskCreate, TaskUpdate, TaskList, TaskGet, Skill, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion |
Takes a feature description, converts it to a user story, implements it via ship-it, and validates with acceptance tests.
Not for: Existing user stories that just need testing (use run-user-stories), or features that don't need formal acceptance criteria.
<when_to_use>
Invoke when user says:
</when_to_use>
The skill accepts the feature description as argument:
| Argument | Example | Description |
|---|---|---|
| Description | /story-to-ship As a user I want to filter recipes by... | Feature description in any format |
| (none) | /story-to-ship | Prompts for feature description |
| Phase | Action | Tool / Skill | Gate |
|---|---|---|---|
| 1 | Parse feature description | AskUserQuestion | User confirms |
| 2 | Create user story | Write | User approves |
| 3 | Implement via ship-it | Skill: ship-it | Per ship-it gates |
| 4 | Completion | - | ship-it success |
Note: ship-it now runs acceptance tests BEFORE committing (Phase 7), so validation is built into the implementation pipeline.
Read .claude/skills/story-to-ship/references/story-phases.md for detailed phase instructions, then execute.
<approval_gates>
| Gate | Phase | Mechanism |
|---|---|---|
| Story details | 1 | AskUserQuestion: Confirm area, preconditions, etc. |
| Story approval | 2 | AskUserQuestion: Approve story before saving |
| Implementation | 3 | All ship-it gates apply (includes validation) |
Note: Validation gate is now part of ship-it Phase 7, before commit.
</approval_gates>
