Specs

Specs bring Kiro's structured planning workflow to the web. Instead of jumping straight into code, you work with the agent to produce a plan—requirements, design, and tasks—then have the agent implement it and open a pull request for you. You review and refine the entire plan directly in your browser.

Kiro Web supports the same spec types as the IDE:

• Feature — Build a new feature. The agent gathers requirements, proposes a technical design, and breaks the work into discrete tasks.
• Bug — Diagnose and fix a bug. The agent root-causes the issue, designs a surgical fix, and plans tasks that prevent regressions.
• Quick Plan — Generate requirements, design, and tasks in a single pass. You answer clarifying questions up front and land directly on a task list, without approval gates between phases.

1. Go to app.kiro.dev and start a new session.
2. Select one or more repositories using Select repo at the bottom of the chat input. You can add multiple repositories to a single spec session, and the agent will plan and coordinate changes across all of them.
3. Choose Spec from the chat input box, then describe what you want to build or fix.

Every spec produces three artifacts that you review directly in your browser:

• requirements.md — user stories and acceptance criteria. A Bug spec produces a bugfix.md instead, a bugfix analysis that captures the current defect, the expected behavior, and the behavior that must stay unchanged to prevent regressions
• design.md — technical architecture and implementation approach
• tasks.md — a discrete, trackable list of implementation tasks

As you work with the agent, you can open each artifact in the browser to review it. Chat with Kiro about the plan to make changes—ask it to add a requirement, rethink part of the design, or adjust the task breakdown—and the agent updates the artifacts in place.

To keep an artifact, share it, or continue working with it in the Kiro IDE, open the artifact in the browser and select the Download button to save the .md file to your local machine.

Once you're happy with the plan, the agent implements it during the session. You start the work using buttons, not by prompting the agent:

• Run all tasks — use the global Run all control to have the agent work through the entire task list.
• Run specific tasks — from the tasks.md view, select an individual task to have the agent work on just that step.

When the work is complete, the agent opens a pull request for your changes, with a description of what was done. You can continue to provide feedback and have the agent push updates.

If you've used specs in the Kiro IDE, a few things work differently on the web:

• You choose Spec from the chat input box, rather than from a dedicated Specs pane.
• You can add multiple repositories to a single spec session, and the agent plans across all of them.
• You review and edit the artifacts in your browser, and can download them to your local machine.

For the full IDE workflow, see Specs in the IDE.