スキル 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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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.