Back to Details

fusion-issue-author-user-story

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Author User Story Issue

撰写用户故事议题

Dependency

依赖项

Requires 
fusion-issue-authoring
as the top-level orchestrator for classification, shared gates, and publish flow.
需要以
fusion-issue-authoring
作为顶层编排器，用于分类、共享校验门控及发布流程。

When to use

使用场景

Use this skill when the request is primarily about user workflow and behavior from a specific role perspective.
当请求主要围绕特定角色视角下的用户工作流与行为时，使用此技能。

When not to use

禁用场景

Do not use this skill for pure bug reports, generic feature specs without user narrative, or technical enablement tasks.
请勿将此技能用于纯Bug报告、无用户叙事的通用功能规格说明，或技术赋能任务。

Required inputs

必填输入

  • User role and workflow context
  • Story goal (
    As a... I want... so that...
    )
  • Key scenarios and success criteria
  • 用户角色与工作流上下文
  • 故事目标（
    作为... 我希望... 以便...
    格式）
  • 关键场景与成功标准

Instructions

操作步骤

  1. Confirm routed type is 
    User Story
    .
  2. Draft locally in 
    .tmp/USER-STORY-<context>.md
    .
  3. Structure draft with:
    • Story statement
    • Context/pain points
    • Functional requirements
    • Scenarios (
      Given/When/Then
      )
    • Validation approach
  4. Ensure scenarios are testable and role-centered.
  5. Return draft summary for orchestrator review/publish flow.
Template fallback:
  • skills/fusion-issue-author-user-story/assets/issue-templates/user-story.md
  1. 确认路由类型为
    User Story
    。
  2. 在本地
    .tmp/USER-STORY-<context>.md
    文件中草拟内容。
  3. 草拟内容需包含以下结构：
    • 故事陈述
    • 上下文/痛点
    • 功能需求
    • 场景（
      给定/当/则
      格式）
    • 验证方法
  4. 确保场景可测试且以角色为中心。
  5. 返回草拟摘要，供编排器审核/进入发布流程。
模板回退方案：
  • skills/fusion-issue-author-user-story/assets/issue-templates/user-story.md

Expected output

预期输出

  • Draft file path in 
    .tmp/
  • Proposed title/body summary
  • Story-specific scenario and validation summary
  • .tmp/
    目录下的草拟文件路径
  • 建议的标题/正文摘要
  • 故事专属的场景与验证摘要

Safety & constraints

安全与约束

Do not perform mutation directly; mutation stays in 
fusion-issue-authoring
.
请勿直接执行变更操作；变更操作需在
fusion-issue-authoring
中完成。