This skill is used during the verification phase to generate structured defect report body(for external systems such as Jira/ZenTao/Linear/GitHub Issue), and to ensure that defect information can flow back into the Spec Pack's report-*.md(as delivery-blocking and risk evidence).
Important boundaries:
- Prohibitedto add within the Spec Pack
verification/bugs/**or any bug file/directory.- The output of this skill is mainly "conversation output", used for pasting into an external defect system; after the external defect is created, information such as the ID/link needs to be written back to
report-*.md's "Defect List".
Inputs and gates (must be followed)
REQUIRED SUB-SKILL: currently executing spec-context to obtain context, and echo in the conversation FEATURE_DIR=...(allowed (reuse)）。
- locate first, then write back: if the defect ID/link needs to be written back to
report-*.md, you must first obtainspec-contextviaFEATURE_DIR; if it fails, stop, and do not guess the path. - Required project-level memory：
project/memory/product.md、project/memory/tech.md、project/memory/glossary.md; if missing, must writeCONTEXT GAP。 - Minimum factual inputs(to be provided by the user, or extracted from context):
- Phenomenon description (actual vs expected)
- Reproduction steps (reproducible by others)
- Environment information (OS/browser/device/environment/version or build)
- Impact assessment (user impact/frequency/business impact/data impact/security impact)
- Evidence (screenshots/screen recordings/logs/network request summaries; may be empty but the reason must be stated)
- Associated test case ID: at least 1
TC-*(fromverification/usecase.md）
Output (conversation output, no bug file written to disk)
This skill outputs two parts:
- Defect report body (Markdown): generated according to the template, can be pasted directly into an external defect system.
- Report write-back snippet (Markdown): used for pasting into
{FEATURE_DIR}/verification/report-{date}-{version}.md's "Defect List / Blocking Items" section, with fields including:- External defect ID + link + status + severity/priority
- Associated
TC-* - Whether it blocks delivery (aligned with
test-plan.md's Exit Criteria)
Template source (mandatory):
assets/bug_report_templates.md
Execution points (mandatory)
- The title must be specific：
[模块/能力] 在 [条件/操作] 下出现 [错误](avoid "there is a bug/it doesn't work"). - Reproduction steps must be executable: each step should be specific, avoid "click the button and then an error occurs".
- The environment must be traceable: at least include OS, browser/device, environment (Dev/Staging/Prod), and version/build.
- Handling of sensitive information: logs/screenshots must be redacted; for security issues, avoid providing directly exploitable attack code.
- Bound to test cases: a defect must be associated with at least one
TC-*, otherwise it will causereportto be untraceable.
DoD self-check
- Title is specific and searchable
- Reproduction steps can be reproduced by a third party
- Expected vs actual is clear
- Environment information is complete and traceable
- Severity / Priority has been provided
- Linked to
TC-* - Evidence has been provided or the reason for its absence has been stated
- The impact on delivery and whether it is blocking have been provided