mcpField
F
fusion-issue-author-task

fusion-issue-author-task

github.com/equinorDevelopment930 installs
Repository

About fusion-issue-author-task

fusion-issue-author-task is a deprecated skill for drafting task issues covering planning, research, specifications, testing, documentation, and other enablement work. It depends on fusion-issue-authoring for classification and review or publishing, and does not perform issue mutations itself.

Key features

  1. 01Drafts task issue content locally
  2. 02Supports planning and research tasks
  3. 03Uses task-specific templates
  4. 04Maps dependencies and blockers
  5. 05Leaves publishing to the orchestrator

Use cases

  1. 01Draft a research or planning issue
  2. 02Break broad work into checklist items
  3. 03Document task order and blockers

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

CHANGELOG.md
assets/
README.md
assets/issue-templates/
task.documentation.md
task.md
task.planning.md
task.research.md
task.spec.md
task.testing.md
task.ux.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 Task Issue

Dependency

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

When to use

Use this skill for planning, research, specification, migration, testing, documentation, or other enablement work.

When not to use

Do not use this skill when the request is clearly a bug, feature, or user-story issue.

Required inputs

  • Task objective and scope
  • Dependency and ordering constraints

Instructions

  1. Confirm routed type is Task.
  2. Start with a concise checklist of small tasks when request is broad.
  3. For multi-issue requests, define logical order and blockers before drafting.
  4. Draft locally in .tmp/TASK-<context>.md.
  5. Use appropriate task template variant (planning/research/spec/testing/documentation/generic).
  6. Include dependency notes and blocker mapping in the draft.
  7. Return draft summary for orchestrator review/publish flow.

Template fallback:

  • skills/fusion-issue-author-task/assets/issue-templates/task.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.planning.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.research.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.spec.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.ux.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.testing.md
  • skills/fusion-issue-author-task/assets/issue-templates/task.documentation.md

Expected output

  • Checklist (for broad task requests)
  • Draft file path in .tmp/
  • Dependency plan (order + blockers)
  • Task-specific decomposition summary

Safety & constraints

Never create contradictory dependency links. Always model sequencing before adding blockers. Do not perform mutation directly; mutation stays in fusion-issue-authoring.

Comments

Markdown supported