'user-stories' 검색 결과

Turn Airflow Improvement Proposals into practical guides checked against current code, or proposed user stories for design review before implementation. Organize use cases, distinguish verified examples from speculative code, and capture specific design questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create implementation-backed guides for an Airflow proposal
• Explore user stories before a feature is implemented
• Separate implemented features from proposed functionality

Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Breaking a new feature into backlog items
• Defining testable acceptance criteria
• Sharing user needs alongside design references

Agile product ownership for backlog management and sprint execution. Use for writing user stories and acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing a backlog.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an agent needs to write user stories for a project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create and maintain a product or project backlog with prioritized items, acceptance criteria, and estimates. Covers user story writing, MoSCoW prioritization, backlog grooming, item splitting, and status tracking. Use when starting a new project and converting scope into actionable items, during ongoing grooming before sprint planning, re-prioritizing after stakeholder feedback or scope changes, or splitting oversized items into implementable pieces.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BA (Business Analyst) agent. Analyzes requirements and produces 4 artifact files: requirements.md, user-stories.md, acceptance-criteria.md, business-rules.md. Use --srs to load from SRS workflow artifacts (spec.md / brainstorm.md). Part of the Virtual Team Skill pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BA (Business Analyst) agent. Analyzes requirements and produces 4 artifact files: requirements.md, user-stories.md, acceptance-criteria.md, business-rules.md. Use --spec <path> to load requirements from any markdown file. Part of the Virtual Team Skill pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.