Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

fusion-issue-author-task

Estrelas0

Forks0

Atualizado18 de março de 2026 às 21:26

DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update task issues with checklist-first decomposition and dependency-aware sequencing.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

equinor

equinor/fusion-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

10 arquivos

SKILL.md

readonly

name	fusion-issue-author-task
description	DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update task issues with checklist-first decomposition and dependency-aware sequencing.
license	MIT
metadata	{"version":"0.1.3","status":"deprecated","deprecated_at":"2026-03-18","successor":"fusion-issue-authoring","owner":"@equinor/fusion-core","orchestrator":"fusion-issue-authoring","role":"subordinate","tags":["github","issue-authoring","task","deprecated"],"mcp":{"required":["github"]}}

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

Confirm routed type is Task.
Start with a concise checklist of small tasks when request is broad.
For multi-issue requests, define logical order and blockers before drafting.
Draft locally in .tmp/TASK-<context>.md.
Use appropriate task template variant (planning/research/spec/testing/documentation/generic).
Include dependency notes and blocker mapping in the draft.
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.

Mais deste repositório

mesmo repositório

fusion-github-review-resolution

equinor/fusion-skills

Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.

2026-07-030

fusion-mcp

equinor/fusion-skills

Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.

2026-07-030

fusion-pm-mcp

equinor/fusion-skills

Explain what Fusion PM MCP is and guide setup of the hosted HTTP+OAuth server for its GitHub project-management retrieval tools. USE FOR: setting up or troubleshooting Fusion PM MCP, understanding its issue/PR/milestone tools, filing a setup bug. DO NOT USE FOR: implementing changes to the fusion-pm-mcp service itself, GitHub issue authoring/triage workflows, or general Fusion Framework/docs/EDS retrieval — use `fusion-mcp` for that.

2026-07-030

fusion-infra-cli

equinor/fusion-skills

Provision and migrate Fusion databases using the fusion-infra-cli (finf). USE FOR: provision a database for a service, run SQL migrations, provision PR-specific ephemeral databases, check database state. DO NOT USE FOR: application code changes, service deployments, role management, or infrastructure other than databases.

2026-07-030

fusion-roles-cli

equinor/fusion-skills

Deploy and manage Fusion Roles V2 configuration using the fusion-roles-cli (froles). USE FOR: deploy role config from a JSON file, create roles/bindings/assignments, export current role state, inspect role assignments. DO NOT USE FOR: database provisioning, application code changes, Azure AD group management outside role bindings, or Roles V1 management.

2026-07-030

fusion-skill-authoring

equinor/fusion-skills

Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.

2026-07-030

name	fusion-issue-author-task
description	DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update task issues with checklist-first decomposition and dependency-aware sequencing.
license	MIT
metadata	{"version":"0.1.3","status":"deprecated","deprecated_at":"2026-03-18","successor":"fusion-issue-authoring","owner":"@equinor/fusion-core","orchestrator":"fusion-issue-authoring","role":"subordinate","tags":["github","issue-authoring","task","deprecated"],"mcp":{"required":["github"]}}

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

Confirm routed type is Task.
Start with a concise checklist of small tasks when request is broad.
For multi-issue requests, define logical order and blockers before drafting.
Draft locally in .tmp/TASK-<context>.md.
Use appropriate task template variant (planning/research/spec/testing/documentation/generic).
Include dependency notes and blocker mapping in the draft.
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.