equinor/fusion-skills· MIT 内容可用

fusion-issue-author-task

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

安装

与 skills.sh 相同的 Command / Prompt 安装方式

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.

附带文件

assets/issue-templates/task.documentation.md

## Objective

Describe what documentation needs to be created or updated.

## Audience

Who is this documentation for?

## Scope

- In scope:
- Out of scope:

## Outline

- 

## Done when

- [ ] Documentation is published/updated
- [ ] Links and examples are verified

## Notes

Related issues:

assets/issue-templates/task.md

## Objective

Describe the concrete work to be completed.

## Scope

- In scope:
- Out of scope:

## Deliverables

- 

## Done when

- [ ] 

## Notes

Dependencies/related issues:

assets/issue-templates/task.planning.md

## Objective

Define the planning goal.

## Scope

### In scope

- 

### Out of scope

- 

## Planning output

- Work breakdown
- Estimates
- Milestones / rollout approach

## Done when

- [ ] Plan is documented and reviewed
- [ ] Dependencies and risks are identified

## Notes

Related issues:

assets/issue-templates/task.research.md

## Objective

State the question this research should answer.

## Key questions

- 

## Approach

- Methods/sources:
- Timebox:

## Deliverables

- Findings summary
- Recommendation(s)
- Open questions

## Done when

- [ ] Findings are documented
- [ ] Decision support is shared

## Notes

Related issues:

assets/issue-templates/task.spec.md

## Objective

Define the specification outcome.

## Background

Provide context and constraints.

## Decisions needed

- 

## Proposed design

- Architecture/API/data model changes
- Alternatives considered

## Scope

- In scope:
- Out of scope:

## Done when

- [ ] Spec is documented
- [ ] Stakeholder review is completed

## Notes

Related issues:

assets/issue-templates/task.testing.md

## Objective

Describe what testing this task covers.

## Scope

- Components/features under test:
- Environments:

## Test cases

- [ ] 

## Verification criteria

- [ ] Expected behavior validated
- [ ] Regressions checked

## Notes

Related issues:

assets/issue-templates/task.ux.md

## Objective

Describe the UX problem to solve.

## Context

What user workflow, screen, or interaction is affected?

## Scope

- In scope:
- Out of scope:

## UX deliverables

- User flow and interaction notes
- Wireframes/mockups/prototypes
- UX acceptance criteria

## Validation

- [ ] User journey is validated against the target workflow
- [ ] Accessibility and usability considerations are documented

## Notes

Related issues:

assets/README.md

# Task templates

Type-specific fallback templates for `fusion-issue-author-task`.

## Files

- `issue-templates/task.md`
- `issue-templates/task.planning.md`
- `issue-templates/task.research.md`
- `issue-templates/task.spec.md`
- `issue-templates/task.ux.md`
- `issue-templates/task.testing.md`
- `issue-templates/task.documentation.md`

CHANGELOG.md

# Changelog

## 0.1.3 - 2026-03-18

### patch

- [#98](https://github.com/equinor/fusion-skills/pull/98) [`6bb9cdc`](https://github.com/equinor/fusion-skills/commit/6bb9cdcc1e2e0ed25d562bfd5db4dfab52559c0f) - Deprecate in favor of consolidated `fusion-issue-authoring` skill


  - Set `metadata.status: deprecated` and `metadata.successor: fusion-issue-authoring`
  - Move to `skills/.deprecated/` placement lane
  - Add deprecation notice pointing to the consolidated skill

  Resolves equinor/fusion-core-tasks#802

## 0.1.2 - 2026-03-05

### patch

- [#55](https://github.com/equinor/fusion-skills/pull/55) [`2d346c8`](https://github.com/equinor/fusion-skills/commit/2d346c812b4927ed1fdf17c92d51856d1fdc09c3) - Add required ownership metadata (`metadata.owner`, `metadata.status`) to all skills. Owner is set to `@equinor/fusion-core` (repository default) and status is set according to skill lifecycle (`active` for production skills, `experimental` for early-stage skills). Sponsor metadata was considered but is not required for MVP.


  resolves equinor/fusion-core-tasks#474

## 0.1.1 - 2026-02-20

### patch

- [#23](https://github.com/equinor/fusion-skills/pull/23) [`14b9c99`](https://github.com/equinor/fusion-skills/commit/14b9c9902dbf8bafdae9fe0fc6c08c81dec004b1) - Migrate issue authoring guidance from helper scripts to GitHub MCP-first workflows, including MCP metadata declarations and updated orchestration/ref docs.


  resolves equinor/fusion-skills#21

## 0.1.0 - 2026-02-20

### minor

- [#10](https://github.com/equinor/fusion-skills/pull/10) [`d473723`](https://github.com/equinor/fusion-skills/commit/d4737239be54736e344d74be4ce8271b9be84313) - Adds structured frontmatter metadata for discoverability and clarifies skill relationship semantics.


  Scope delivered:
  - Added `metadata.tags` to affected skills for discoverability.
  - Renamed relationship keys to a clearer schema: `skill_role` → `role`, `required_skill` → `orchestrator`, `sub_skills` → `skills`.
  - Updated dependent role value from `subskill` to `subordinate` to explicitly indicate orchestrator dependency.
  - Updated skill authoring guidance to document `metadata.role`, `metadata.orchestrator`, `metadata.skills`, and `metadata.tags`.

- [#7](https://github.com/equinor/fusion-skills/pull/7) [`2194e7a`](https://github.com/equinor/fusion-skills/commit/2194e7a99f6055dd394dffca6e0e6286d3bb2d41) - Implements `equinor/fusion-core-tasks#395` (sub-task of `#391`) by restructuring issue authoring skills into a top-level orchestrator plus type-specific specialists.


  Refs: `equinor/fusion-core-tasks#391`

  closes equinor/fusion-core-tasks#395

  Scope delivered:
  - `fusion-issue-authoring` is now the orchestration layer for shared gates (classification, labels, assignee, confirmation, publish flow).
  - Added specialist skills: `fusion-issue-author-bug`, `fusion-issue-author-feature`, `fusion-issue-author-user-story`, and `fusion-issue-author-task`.
  - Specialist skills now explicitly depend on `fusion-issue-authoring` and keep only type-specific guidance.
  - Moved fallback templates from shared assets to each specialist skill’s own `assets/issue-templates/`.
  - Added label listing helpers: `list-labels.sh` and `list-labels.ps1`.
  - Hardened relationship scripts for reliable GraphQL calls and idempotent "already linked" handling.