Community程式設計與開發github.com

equinor/fusion-issue-task-planning

規劃並將用戶故事問題分解為有序、可追溯的任務問題草稿,並包含明確的發佈閘門。

fusion-issue-task-planning 是什麼?

此技能專為開發者與 AI 代理設計,能將使用者故事(user-story)問題自動規劃並拆解成一系列有序、可追蹤的任務問題草稿。它不僅確保每個任務都有清晰的依賴與順序,還引入了「發佈閘門」(publish gates)機制,讓使用者能在發佈前審查與確認,避免草率上線。此技能支援 GitHub Issues 等常見問題追蹤平台,並可整合至 Claude Code、Cursor 或 Codex 等開發工具中。透過分析原始問題的描述與需求,它會產生結構化的任務列表,每個任務皆包含標題、描述、標籤與關聯性,從而提升團隊協作效率與專案管理的透明度。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/equinor/fusion-skills/tree/main/skills/fusion-issue-task-planning

Installed? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

fusion-issue-task-planning 是做什麼的?

規劃並將用戶故事問題分解為有序、可追溯的任務問題草稿,並包含明確的發佈閘門。

概覽

此技能用於將大型用戶故事(user story)自動拆解為多個細部任務問題,確保每個任務皆有序排列、彼此可追溯。它會產生任務草稿,並在最終發佈前設置審查關卡(publish gates),讓團隊能驗證內容品質後再正式提交。

使用方式

  1. 輸入:提供一個用戶故事問題的連結或 ID。
  2. 處理:技能會分析該故事的描述、接受標準與相關討論。
  3. 輸出:生成一組任務問題草稿,每個草稿都包含:
    • 明確的標題
    • 詳細的描述
    • 適當的標籤
    • 與原始故事的關聯
  4. 發佈閘門:所有草稿會先儲存為暫存狀態,使用者可審查、修改,確認無誤後再批次發佈。

支援平台

  • GitHub Issues
  • GitLab Issues(即將支援)
  • Jira(計畫中)

環境變數

此技能需要以下環境變數方能正常運作:

  • GITHUB_TOKEN:用於存取 GitHub API 的個人存取權杖。
  • GITHUB_REPO:目標儲存庫的名稱(格式為 owner/repo)。

範例

# 使用 CLI 觸發技能
fusion-issue-task-planning --issue-url "https://github.com/owner/repo/issues/42"

注意事項

  • 任務順序會根據相依性自動決定,但建議最終仍由人工確認。
  • 發佈閘門可設定為自動核准或手動審查,預設為手動。

授權

此專案採用 MIT 授權條款。

Individual skills in this repo

This repo contains 5 individual skills — each has its own dedicated page.

equinor/fusion-github-review-resolution

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.

equinor/fusion-issue-authoring

Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.

equinor/fusion-issue-solving

Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.

equinor/fusion-mcp

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

equinor/fusion-skill-authoring

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.

相關技能