bmad-ticket
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.
توقف واطلب التأكيد قبل التثبيت.
راجع الخطة واحصل على موافقة صريحة من المستخدم قبل تغيير الملفات.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
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 عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "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.
التدقيق الأمني
مخاطر عالية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.
مخاوف أمنية مؤكدة (2)
عوامل الخطر
⚙️ الأوامر الخارجية (50)
🌐 الوصول إلى الشبكة (7)
📁 الوصول إلى نظام الملفات (9)
🔑 متغيرات البيئة (2)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/bmad-code-org-bmad-ticket/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](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/1اقتباس BibTeX
@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
سبب هذا التقييم موثوقية الأدلة: متوسطما الذي يمكنك بناؤه
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 for [problem]. Ask for missing reproduction steps and expected behavior. Show the draft before saving or publishing.
Find ticket [reference] in [initiative]. Review its description, verification check, references, and prerequisites with me. Preserve its identity and do not publish yet.
Split [epic] into implementation entries using [requirement source]. Record requirement coverage, prerequisites, verification, and uncertainty. Validate the proposed set before requesting approval.
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.