Bugfix Specs - Specs - Features - Docs - Kiro Loading image... Product * About Kiro * IDE * CLI * Web * Mobile * Crew * Pricing * Downloads For * Enterprise * Startups * Students Community * Overview * Ambassadors * Discord * Events * Powers * Shop * Showcase Resources * Docs * Blog * Changelog * FAQs * Report a bug * Suggest an idea * Billing support Social * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Feature Specs Bugfix Specs Quick Spec Plan mode Analyze Requirements Correctness Best practices Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Chat Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * Features * * Specs * * Bugfix Specs Copy page View as Markdown Bugfix Specs Copy page View as Markdown The Bugfix Spec models how experienced developers approach bug fixes: identify the root cause, understand what should change, and explicitly preserve what shouldn't. Bugfix Specs provide a structured approach using that workflow, guiding you through root cause analysis, fix design, and regression prevention. Key Benefits Scoped fixes - Explicit constraints ensure only necessary changes are made Regression prevention - Unchanged behavior is documented and tested Documentation - Complete record of the bug, fix, and reasoning for future reference Reliability - Structured workflow prevents common pitfalls of ad-hoc fixes When to Use Bugfix Specs Best for: * Complex bugs requiring root cause analysis * Bugs in critical code paths where regressions are costly * Bugs that need documentation for compliance or team knowledge * Situations where previous fix attempts caused regressions How It Works Bugfix Specs follow the same three-phase workflow as Feature Specs (Requirements → Design → Tasks), but with content tailored specifically for bug fixes: Loading diagram... 1. Bugfix Analysis Phase Instead of a requirements document, you create a bugfix.md that captures: Current Behavior (Defect) * WHEN [condition] THEN the system [incorrect behavior] Expected Behavior (Correct) * WHEN [condition] THEN the system SHALL [correct behavior] Unchanged Behavior (Regression Prevention) * WHEN [condition] THEN the system SHALL CONTINUE TO [existing behavior] This explicit structure ensures Kiro understands not just what's broken, but what must remain working. 2. Design Phase Kiro explores the codebase to root cause the issue and generates a design.md with: * Root cause analysis * Proposed fix approach * Properties to test for: * Current implementation produces incorrect behavior (validates the bug exists) * Fixed implementation produces correct behavior (validates the fix works) * Unchanged implementation continues working (prevents regressions) 3. Tasks Phase Implementation tasks are generated with property-based tests (PBTs) that validate: * The bug is reproducible * The bug is fixed * No regressions are introduced Getting Started IDE CLI Web * Choose Bug Fix from the workflow options on the "Let's build" screen when starting a new session. To switch mid-session, click the agent name in the bottom bar of the chat input and select Bug Fix from the agent picker. * Describe the bug, including: * When the bug occurs (reproduction steps) * What should happen instead * Any constraints (code that shouldn't be modified) * Follow the workflow through analysis, design, and implementation. Learn More Best Practices Tips for effective bug fixing with Bugfix Specs Page updated: August 4, 2026 Design-First Quick Spec