story-workflow
9-phase workflow for implementing user stories. Covers requirements through verification.
- License 许可
- MIT
- 最近更新
- 2026-03-11
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- story-workflow
- description
- 9-phase workflow for implementing user stories. Covers requirements through verification.
- disable-model-invocation
- true
02 资源文件 7
- 参考文档prior-auth-letter-drafter_audit_result_v1.json12.1 KB
- 参考文档references/carrier_requirements.json4.1 KB
- 参考文档references/clinical_phrases.md4.4 KB
- 参考文档references/guidelines.md1.3 KB
- 参考文档references/requirements.txt173 B
- 参考文档requirements.txt17 B
- 脚本scripts/main.py10.0 KB
03 SKILL.md 正文
User Story Workflow
Follow the phases in order.
Phase 1-2: Requirements & Assessment
Follow /mandatory-gates (Gates 1-3) first.
Additionally:
- Identify all acceptance criteria
- Break down into subtasks
- Evaluate UX impact — does this change visible user behavior?
Wait for scope confirmation before proceeding (Gate 3)
Phase 3: Implementation
# Create branch and push immediately
git checkout -b feat/[short-description]
git commit --allow-empty -m "chore: init branch" && git push -u origin HEAD
# Commit after EVERY file change
git add <file> && git commit -m "WIP: description" && git push
Work through subtasks in order. Commit frequently.
Phase 4: Validation
Run /code-quality before pushing.
If Playwright is available:
- Walk through the user flow end-to-end
- Verify all acceptance criteria
- Save screenshots to
/tmp/agent-artifacts/screenshots/
Phase 5: Create PR and Wait for CI
Use /pr-creation to create the PR.
wait-for-checks <PR_NUMBER>
Phase 6: Resume — CI & Review
When resumed after CI:
- CI failed → Fix, push, end response
- CI passed → Handle review comments with
/review-handling
Phase 7-8: Preview & Verification
If preview is available, trigger it, verify acceptance criteria on preview.
Phase 9: Request Review
Post a summary mapping each acceptance criterion to evidence.
04 同仓库更多 Skills
rfs-proposal
File a Request for Skill (RFS) when a skill gap is detected during execution.
review-handling
Process review comments from AI review or human reviewers. Evaluate, respond, and resolve or escalate.
pr-creation
Create GitHub pull requests with proper format.
playwright-verify
Browser verification using Playwright MCP. Navigate, interact, screenshot.
merge-conflicts
Resolve merge conflicts by rebasing. Use when PR mergeable status is CONFLICTING.
mandatory-gates
Pre-implementation gates. MUST be followed before writing any code. Investigation, confidence assessment, and scope confirmation.