mcpField
F
fusion-issue-author-user-story

fusion-issue-author-user-story

github.com/equinorDevelopment809 installs
Repository

About fusion-issue-author-user-story

A deprecated skill for drafting user-story issues from a role’s workflow and goals. It relies on `fusion-issue-authoring` for classification and publishing, and does not make changes directly.

Key features

  1. 01Role-centered story drafts
  2. 02Given/When/Then scenarios
  3. 03Testable success criteria
  4. 04Local draft in `.tmp/`

Use cases

  1. 01Describe a workflow need from a user role
  2. 02Prepare a story for orchestrator review

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/equinor/fusion-skills --skill fusion-issue-author-user-story

After installing, type/fusion-issue-author-user-storyin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CHANGELOG.md
assets/
README.md
assets/issue-templates/
user-story.md

Details

From the project README

DEPRECATED: This skill has been consolidated into fusion-issue-authoring. Install only fusion-issue-authoring for full bug/feature/user-story/task authoring capability. See equinor/fusion-core-tasks#802 for details.

Author User Story Issue

Dependency

Requires fusion-issue-authoring as the top-level orchestrator for classification, shared gates, and publish flow.

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.

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

Expected output

  • Draft file path in .tmp/
  • Proposed title/body summary
  • Story-specific scenario and validation summary

Safety & constraints

Do not perform mutation directly; mutation stays in fusion-issue-authoring.

Comments

Markdown supported