Lab 3: Spec Mini

← Back to overview

Goal

For a small extension of the Kanban board from Lab 2, you have Kiro create a complete spec — that is requirements.md, design.md and tasks.md — and stop before executing the tasks (no code). This makes the difference from fast chat mode tangible.

Preparation

• The project from Lab 2 (Kanban board) opened.
• In Kiro, select spec mode (instead of chat).

Step 1 – Start the spec

Formulate the desired feature. Example:

Create a spec for a filter feature in the Kanban board:
users should be able to filter the cards by due date
(e.g. "due today only", "this week", "all").
Generate only the requirements for now. No code yet.

Step 2 – Review requirements.md

• Kiro generates requirements.md with user stories and acceptance criteria (often in EARS notation: "WHEN … THEN the system shall …").
• Read together: is the "what" complete and understandable?
• Refine if needed (e.g. "Add a criterion for the empty filter state").

Step 3 – Generate design.md

Now create the design (design.md) for this feature:
data flow, affected functions/structures and how the filter is
integrated into the existing board. Still no code.

• Review design.md: architecture, data flow, possibly a small diagram.

Step 4 – Generate tasks.md

Now we have Kiro generate the task list as well — the third and final spec file:

Now create the task list (tasks.md) for this feature.
Only list and sequence the tasks – do NOT execute the tasks yet
and do not write any code.

• Review tasks.md: discrete, traceable tasks with order and dependencies.
• Now all three artifacts exist: requirements.md (what) → design.md (how) → tasks.md (execution plan).

Step 5 – Deliberately do NOT run the tasks

• We do not proceed to implementation. So do not click "Start task" / "Run all tasks" / "Implement", even if Kiro offers it.
• Instead, take your time to review the three created files: requirements.md (the what), design.md (the how) and tasks.md (the plan).
• Note briefly for yourself: what is different here from chat mode, where code comes immediately?

Expected result

Three comprehensible artifacts (requirements.md, design.md, tasks.md) in the .kiro/specs/… folder that describe the feature and contain an execution plan — without any code being created (the tasks were not run).

Key takeaways

• Spec-driven forces a "thinking pause" before coding (Think before Typing).
• The three artifacts: requirements (what) → design (how) → tasks (execution).
• Results are traceable and can be reviewed/approved by teams (auditable).
• Spec-driven for production, chat mode for quick prototypes.