mcpField
F
fusion-issue-author-feature

fusion-issue-author-feature

github.com/equinorDevelopment812 installs
Repository

About fusion-issue-author-feature

fusion-issue-author-feature is a deprecated skill for drafting issues about new capabilities or enhancements. It requires fusion-issue-authoring for orchestration and review or publishing, and does not make issue changes directly.

Key features

  1. 01Drafts feature issue content locally
  2. 02Defines scope and non-goals
  3. 03Records functional requirements
  4. 04Adds acceptance criteria and risks
  5. 05Leaves publishing to the orchestrator

Use cases

  1. 01Draft an issue for a new capability
  2. 02Specify boundaries and non-goals
  3. 03Record feature criteria and dependencies

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

CHANGELOG.md
assets/
README.md
assets/issue-templates/
feature.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 Feature 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 for a new capability or enhancement.

When not to use

Do not use this skill for bugs, user stories centered on role narratives, or generic technical tasks.

Required inputs

  • Feature intent and value
  • Scope and non-goals
  • Success criteria

Instructions

  1. Confirm routed type is Feature.
  2. Draft locally in .tmp/FEATURE-<context>.md.
  3. Structure draft with:
    • Story/problem statement
    • Scope (in/out)
    • Functional requirements
    • Acceptance criteria
    • Dependencies/risks
  4. Check that scope boundaries and non-goals are explicit.
  5. Return draft summary for orchestrator review/publish flow.

Template fallback:

  • skills/fusion-issue-author-feature/assets/issue-templates/feature.md

Expected output

  • Draft file path in .tmp/
  • Proposed title/body summary
  • Feature-specific scope and acceptance summary

Safety & constraints

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

Comments

Markdown supported