[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACAQD2CFGD6ZP7EAGDNFBH":3,"skill-same:01M7ACAQD2CFGD6ZP7EAGDNFBH":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7ACAQD2CFGD6ZP7EAGDNFBH","speckit-bugfix-report",null,"Capture a bug and trace it back to the relevant spec, plan, and task artifacts","cadugevaerd\u002Fgrill-with-docs","cadugevaerd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63358082?v=4","01M7AC7XM4CZJ31SYHN7K3WARC","Carlos Eduardo Gevaerd Araujo","01M7AC7XMXXNZBHQNVQKVN8DB7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-bugfix-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: speckit-bugfix-report\ndescription: Capture a bug and trace it back to the relevant spec, plan, and task\n  artifacts\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: bugfix:commands\u002Fspeckit.bugfix.report.md\n---\n\n# Report Bug\n\nCapture a bug discovered during implementation and trace it back to the relevant specification artifacts. Produces a structured bug report that maps the issue to spec requirements, plan sections, and tasks.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty). The user describes the bug — what went wrong, error messages, unexpected behavior, or a gap discovered during implementation.\n\n## Prerequisites\n\n1. Verify a spec-kit project exists by checking for `.specify\u002F` directory\n2. Locate the current feature's spec directory (by branch name or most recently modified)\n3. Verify at least `spec.md` exists\n\n## Outline\n\n1. **Load artifacts**: Read from the current feature directory:\n   - **Required**: `spec.md` (the specification)\n   - **Optional**: `plan.md`, `tasks.md`, `research.md`, `data-model.md`\n\n2. **Analyze the bug**: From the user's description, classify the bug:\n\n   | Bug Type | Description | Example |\n   |----------|-------------|---------|\n   | Spec gap | Requirement missing from spec | Auth flow doesn't handle expired tokens |\n   | Spec conflict | Two requirements contradict | \"Must be stateless\" vs \"Must track sessions\" |\n   | Implementation drift | Code diverges from spec | Spec says REST, code uses GraphQL |\n   | Untested flow | Edge case not covered in success criteria | Concurrent user updates not handled |\n   | Dependency issue | External dependency behaves differently than assumed | API response format changed |\n\n3. **Trace to artifacts**: Map the bug to specific sections in each artifact:\n   - **spec.md**: Which user story, requirement, or success criterion is affected?\n   - **plan.md**: Which plan section covers this area?\n   - **tasks.md**: Which task(s) relate to this area? Are any marked complete that shouldn't be?\n\n4. **Generate bug report**: Output a structured report:\n\n   ```markdown\n   # Bug Report: [Short Title]\n\n   **Type**: [Spec gap | Spec conflict | Implementation drift | Untested flow | Dependency issue]\n   **Severity**: [Critical | High | Medium | Low]\n   **Feature**: [Feature name\u002Fbranch]\n   **Reported**: [DATE]\n\n   ## Description\n   [User's bug description, clarified and structured]\n\n   ## Artifact Traceability\n\n   ### spec.md\n   - **Affected user story**: [Story N — title]\n   - **Affected requirements**: [List specific requirements]\n   - **Gap identified**: [What is missing or wrong in the spec]\n\n   ### plan.md\n   - **Affected sections**: [List plan sections]\n   - **Impact**: [What needs to change in the plan]\n\n   ### tasks.md\n   - **Affected tasks**: [Task IDs and descriptions]\n   - **False completions**: [Tasks marked done that need reopening]\n   - **Missing tasks**: [New tasks needed to fix the bug]\n\n   ## Root Cause Analysis\n   [Why this bug exists — was it a spec oversight, changed requirement, or implementation error?]\n\n   ## Recommended Fix\n   1. Run `\u002Fspeckit.bugfix.patch` to update spec artifacts\n   2. Run `\u002Fspeckit.bugfix.verify` to confirm consistency\n   3. Resume `\u002Fspeckit.implement` to apply the code fix\n   ```\n\n5. **Save report**: Write the bug report to `specs\u002F{feature}\u002Fbugs\u002FBUG-{NNN}.md` where `{NNN}` is the next sequential bug number. Create the `bugs\u002F` directory if it does not exist.\n\n6. **Report**: Output the bug report and suggest next steps.\n\n## Rules\n\n- **Always trace to artifacts** — every bug must map to at least one spec section\n- **Never modify spec artifacts** — this command only reports, use `\u002Fspeckit.bugfix.patch` to make changes\n- **Sequential numbering** — bug reports are numbered BUG-001, BUG-002, etc.\n- **Classify accurately** — distinguish between spec gaps (missing requirements) and implementation drift (code doesn't match spec)\n- **Be specific** — reference exact user story numbers, requirement text, and task IDs","# Report Bug\n\nCapture a bug discovered during implementation and trace it back to the relevant specification artifacts. Produces a structured bug report that maps the issue to spec requirements, plan sections, and tasks.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty). The user describes the bug — what went wrong, error messages, unexpected behavior, or a gap discovered during implementation.\n\n## Prerequisites\n\n1. Verify a spec-kit project exists by checking for `.specify\u002F` directory\n2. Locate the current feature's spec directory (by branch name or most recently modified)\n3. Verify at least `spec.md` exists\n\n## Outline\n\n1. **Load artifacts**: Read from the current feature directory:\n   - **Required**: `spec.md` (the specification)\n   - **Optional**: `plan.md`, `tasks.md`, `research.md`, `data-model.md`\n\n2. **Analyze the bug**: From the user's description, classify the bug:\n\n   | Bug Type | Description | Example |\n   |----------|-------------|---------|\n   | Spec gap | Requirement missing from spec | Auth flow doesn't handle expired tokens |\n   | Spec conflict | Two requirements contradict | \"Must be stateless\" vs \"Must track sessions\" |\n   | Implementation drift | Code diverges from spec | Spec says REST, code uses GraphQL |\n   | Untested flow | Edge case not covered in success criteria | Concurrent user updates not handled |\n   | Dependency issue | External dependency behaves differently than assumed | API response format changed |\n\n3. **Trace to artifacts**: Map the bug to specific sections in each artifact:\n   - **spec.md**: Which user story, requirement, or success criterion is affected?\n   - **plan.md**: Which plan section covers this area?\n   - **tasks.md**: Which task(s) relate to this area? Are any marked complete that shouldn't be?\n\n4. **Generate bug report**: Output a structured report:\n\n   ```markdown\n   # Bug Report: [Short Title]\n\n   **Type**: [Spec gap | Spec conflict | Implementation drift | Untested flow | Dependency issue]\n   **Severity**: [Critical | High | Medium | Low]\n   **Feature**: [Feature name\u002Fbranch]\n   **Reported**: [DATE]\n\n   ## Description\n   [User's bug description, clarified and structured]\n\n   ## Artifact Traceability\n\n   ### spec.md\n   - **Affected user story**: [Story N — title]\n   - **Affected requirements**: [List specific requirements]\n   - **Gap identified**: [What is missing or wrong in the spec]\n\n   ### plan.md\n   - **Affected sections**: [List plan sections]\n   - **Impact**: [What needs to change in the plan]\n\n   ### tasks.md\n   - **Affected tasks**: [Task IDs and descriptions]\n   - **False completions**: [Tasks marked done that need reopening]\n   - **Missing tasks**: [New tasks needed to fix the bug]\n\n   ## Root Cause Analysis\n   [Why this bug exists — was it a spec oversight, changed requirement, or implementation error?]\n\n   ## Recommended Fix\n   1. Run `\u002Fspeckit.bugfix.patch` to update spec artifacts\n   2. Run `\u002Fspeckit.bugfix.verify` to confirm consistency\n   3. Resume `\u002Fspeckit.implement` to apply the code fix\n   ```\n\n5. **Save report**: Write the bug report to `specs\u002F{feature}\u002Fbugs\u002FBUG-{NNN}.md` where `{NNN}` is the next sequential bug number. Create the `bugs\u002F` directory if it does not exist.\n\n6. **Report**: Output the bug report and suggest next steps.\n\n## Rules\n\n- **Always trace to artifacts** — every bug must map to at least one spec section\n- **Never modify spec artifacts** — this command only reports, use `\u002Fspeckit.bugfix.patch` to make changes\n- **Sequential numbering** — bug reports are numbered BUG-001, BUG-002, etc.\n- **Classify accurately** — distinguish between spec gaps (missing requirements) and implementation drift (code doesn't match spec)\n- **Be specific** — reference exact user story numbers, requirement text, and task IDs",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","bugfix:commands\u002Fspeckit.bugfix.report.md","Requires spec-kit project structure with .specify\u002F directory","main","dd561c2e23614861198af1b46cc720d1b0fb2cf0",".claude\u002Fskills\u002Fspeckit-bugfix-report","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs","https:\u002F\u002Fgithub.com\u002Fcadugevaerd","2026-09-28 01:22:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add cadugevaerd\u002Fgrill-with-docs --skill speckit-bugfix-report",{"tool":40,"command":41},"bunx","bunx skills add cadugevaerd\u002Fgrill-with-docs --skill speckit-bugfix-report",{"tool":43,"command":44},"pnpm","pnpm dlx skills add cadugevaerd\u002Fgrill-with-docs --skill speckit-bugfix-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-bugfix-report\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7ACCWNYYQVH259P3X96A3PS","offline-presentation-fixture","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Forchestration\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7ACCS4KGQ0J2V3T60DTETGD","grill-with-docs","Entrevista decisões arquiteturais por work item isolado, mantém feature plan-only e oferece hotfix-fast executável com HOTFIX-GO fail-closed.","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ACCMCXGYXGXSM9FXNECN2G","grill-partition","Particiona tasks.md em subfases file-disjuntas e emite o Execution DAG versionado da etapa partition, de forma determinística e sem julgamento de modelo.","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fgrill-partition\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ACCH73N28NESB337VHEC0R","grill-implement-parallel","Orquestra os workers não-frontier da etapa implement-parallel sobre o Execution DAG, com worktree isolado por worker e receipt submetido apenas pelo leader.","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fgrill-implement-parallel\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ACCDSD9CGXTJDA87C269NZ","speckit-verify-review-ship-verify","Run post-convergence executable gates and diff hygiene checks","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-verify-review-ship-verify\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ACCBFXR7JX9RN0PGRAZTA0","speckit-verify-review-ship-v","https:\u002F\u002Fgithub.com\u002Fcadugevaerd\u002Fgrill-with-docs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-verify-review-ship-v\u002FSKILL.md",[],[]]