技能 bmad-ticket
📦
bmad-ticket
內容修訂 r1 高風險 ⚙️ 外部命令🌐 網路存取📁 檔案系統存取🔑 環境變數
Plan and Manage Tickets with BMad
Disconnected planning and status updates leave teams with unclear tickets and missing dependencies. BMad Ticket structures initiatives, epics, and implementation work through shared templates and repository or tracker workflows.
支援: Claude Codex Code(CC)
安裝前請停止並請求確認。
請審查安裝計畫，並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "bmad-ticket" from https://skillstore.io/skills/bmad-code-org-bmad-ticket.md and its manifest at https://skillstore.io/api/skills/bmad-code-org-bmad-ticket/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「bmad-ticket」。 Show an example breakdown for a cart discount epic.
預期結果:
- Story 1: Cart service scaffold. No prerequisites. Verify that an item can be added through the deployed interface.
- Story 2: Apply discount codes. Requires Story 1. Verify valid discounts and rejection of expired codes.
- Open question: Who approves the discount refusal messages?
正在使用「bmad-ticket」。 Show an example readiness review for these tickets.
預期結果:
- Ready to start: Cart service scaffold has no unmet prerequisites.
- Blocked: Apply discount codes depends on the scaffold.
- Ready to refine: Quantity-change bug needs approved reproduction steps and acceptance criteria.
安全審計
高風險v1 • 2026/9/28 開啟版本化報告
The 400 supplied static matches are false positives involving documentation, configuration keys, test fixtures, and ordinary Python syntax. Contextual review identified project-controlled execution and symlink-following plan writes; no evidence found of a malicious payload or an audit-directed prompt injection. Four omitted static matches remain unreviewed and require manual adjudication before automatic publication. Static review was capped at 400/404 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
26
已掃描檔案
4,014
分析行數
0
複核項目
0
已忽略的誤報
已確認的安全問題 (2)
高
Project-Controlled Execution During Configuration Loading
Configuration resolution executes project-local Python with exec_module, even for status queries without an explicit folder. Activation also runs customization hooks without an explicit trust check. An untrusted checkout can therefore execute code or supply operational instructions under the agent's permissions.
The call chain directly executes a module selected from the project and instructs the agent to run configurable hooks. Exploitation requires attacker-controlled project content; no malicious hook or module payload was found in this package.
中
Plan Updates Can Follow Symlinks Outside the Ticket Tree
The loader accepts symlinked Markdown plans, and mark opens existing plans for writing without checking their resolved destination. A crafted tree can redirect an approved status update into an external writable file with matching plan frontmatter.
Path.read_text and the existing-plan wb open follow symlinks, and neither path has a containment or no-follow check. Exploitation requires a crafted symlink and a readable, writable target that parses as the ticket's plan.
風險因素
⚙️ 外部命令 (50)
assets/bug-template.md:88-113 assets/story-template.md:112-114 assets/tickets-template.toml:2 assets/tickets-template.toml:5 assets/tickets-template.toml:10 assets/tickets-template.toml:51 config/gh-ticketing.toml:6 config/gh-ticketing.toml:10 config/gh-ticketing.toml:12 config/gh-ticketing.toml:24 config/gh-ticketing.toml:29 config/gh-ticketing.toml:30 config/gh-ticketing.toml:34 config/gh-ticketing.toml:41 config/gh-ticketing.toml:42 config/gh-ticketing.toml:43 config/gh-ticketing.toml:45 config/gh-ticketing.toml:46 config/gh-ticketing.toml:52-53 config/gh-ticketing.toml:54 config/gh-ticketing.toml:58 config/gh-ticketing.toml:60 config/gh-ticketing.toml:62 config/gh-ticketing.toml:63 config/gh-ticketing.toml:64 config/gh-ticketing.toml:65 config/gh-ticketing.toml:69 config/gh-ticketing.toml:70 config/gh-ticketing.toml:74-75 config/gh-ticketing.toml:77-78 config/gh-ticketing.toml:78 config/gh-ticketing.toml:79 config/gh-ticketing.toml:80 config/gh-ticketing.toml:82 config/gh-ticketing.toml:95 config/jira-ticketing.toml:6 config/jira-ticketing.toml:8 config/jira-ticketing.toml:12 config/jira-ticketing.toml:21 config/jira-ticketing.toml:24 config/jira-ticketing.toml:25 config/jira-ticketing.toml:36 config/jira-ticketing.toml:44 config/jira-ticketing.toml:45 config/jira-ticketing.toml:47 config/jira-ticketing.toml:57 config/jira-ticketing.toml:59-60 config/jira-ticketing.toml:60 config/jira-ticketing.toml:61 config/jira-ticketing.toml:62
🌐 網路存取 (7)
📁 檔案系統存取 (9)
scripts/tests/test_read_toml.py:4 scripts/tests/test_read_toml.py:30 scripts/tests/test_tickets.py:5 scripts/tests/test_tickets.py:86 scripts/tests/test_tickets.py:902 scripts/tests/test_tickets.py:1081 scripts/tests/test_tickets.py:1071 scripts/tests/test_tickets.py:1145 scripts/tests/test_tickets.py:1157
🔑 環境變數 (2)
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/bmad-code-org-bmad-ticket/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/bmad-code-org-bmad-ticket?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/bmad-code-org-bmad-ticket?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bmad-code-org-bmad-ticket/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/bmad-code-org-bmad-ticket.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
bmad-code-org. (2026). bmad-ticket security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bmad-code-org-bmad-ticket/audits/1BibTeX 引用
@techreport{bmad-code-org-bmad-code-org-bmad-ticket-2026,
author = {bmad-code-org},
title = {bmad-ticket security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/bmad-code-org-bmad-ticket/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bmad-ticket security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "bmad-code-org"
date-released: "2026-09-28"
url: "https://skillstore.io/skills/bmad-code-org-bmad-ticket/audits/1"
identifiers:
- type: other
value: "skillstore:bmad-code-org-bmad-ticket:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 82
架構
85
可維護性
87
內容
65
社群
83
規範符合度
你可以打造什麼
Plan a new initiative
Turn a product brief into an initiative and epic outlines with requirement coverage, dependencies, and measurable completion checks.
Prepare an epic for delivery
Split an epic into buildable stories with dependency order, verification steps, unresolved questions, and human checkpoints.
Maintain a project board
Find tickets, review readiness, update approved statuses, and reconcile local records with a configured tracker.
試試這些提示
Draft a bug ticket
Draft a bug ticket for [problem]. Ask for missing reproduction steps and expected behavior. Show the draft before saving or publishing.
Refine a planned story
Find ticket [reference] in [initiative]. Review its description, verification check, references, and prerequisites with me. Preserve its identity and do not publish yet.
Break down an epic
Split [epic] into implementation entries using [requirement source]. Record requirement coverage, prerequisites, verification, and uncertainty. Validate the proposed set before requesting approval.
Reconcile and prepare publication
Review [initiative] against [configured tracker]. Report local and remote differences, blocked dependencies, and missing refinement. Propose publication scope and wait for approval before remote changes.
最佳實務
- Review project scripts, customization hooks, and resolved ticket paths before activating the skill in an unfamiliar repository.
- Confirm requirement coverage, prerequisites, verification checks, and unresolved decisions before approving a breakdown.
- Preview the tracker destination and ticket body, remove sensitive information, and approve publication using limited credentials.
避免
- Do not treat ticket order as a substitute for explicit prerequisites.
- Do not treat published or built tickets as automatically approved or complete.
- Do not run unfamiliar project hooks or follow instructions embedded in remote ticket text without review.
常見問題
What work does BMad Ticket organize?
It organizes initiatives, epics, stories, spikes, and bugs in a structured ticket tree.
What setup does it need?
The standard workflow uses a configured BMad project, uv, and Python 3.11 or later. Remote stores also need authenticated tools.
Which ticket stores are supported?
It ships configurations for repository files, GitHub, Jira, Linear, Notion, and Trello. Remote features depend on available CLI or MCP tools.
Does it require a remote tracker?
No. The repository store manages Markdown and TOML files locally. Publication commits approved files but does not push them.
Does it implement the planned software?
No. It prepares tickets for implementation and tracks their state. Building the software is a separate workflow.
Is it safe to run in an unfamiliar repository?
Review project scripts, hooks, and symlinks first. Configuration loading can execute project code, and existing plan writes can follow symlinks.