Spirit of Kiro
A game built with and powered by generative AI by the Kiro team — Kiro's own public showcase project.
Reviewed 2 months ago · Jul 18, 2026
- Stars
- 942
- Contributors
- 6
- Open issues
- 13
- Age
- 1.3 years
- Last push
- 2 months ago
- Latest release
- —
View weekly commit data
| Week starting | Commits |
|---|---|
| Aug 30, 2026 | 0 |
| Aug 23, 2026 | 0 |
| Aug 16, 2026 | 0 |
| Aug 9, 2026 | 0 |
| Aug 2, 2026 | 0 |
| Jul 26, 2026 | 0 |
| Jul 19, 2026 | 0 |
| Jul 12, 2026 | 3 |
| Jul 5, 2026 | 0 |
| Jun 28, 2026 | 0 |
| Jun 21, 2026 | 0 |
| Jun 14, 2026 | 0 |
| Jun 7, 2026 | 0 |
| May 31, 2026 | 0 |
| May 24, 2026 | 0 |
| May 17, 2026 | 0 |
| May 10, 2026 | 0 |
| May 3, 2026 | 0 |
| Apr 26, 2026 | 0 |
| Apr 19, 2026 | 0 |
| Apr 12, 2026 | 0 |
| Apr 5, 2026 | 0 |
| Mar 29, 2026 | 0 |
| Mar 22, 2026 | 0 |
| Mar 15, 2026 | 0 |
| Mar 8, 2026 | 0 |
| Mar 1, 2026 | 0 |
| Feb 22, 2026 | 0 |
| Feb 15, 2026 | 0 |
| Feb 8, 2026 | 0 |
| Feb 1, 2026 | 0 |
| Jan 25, 2026 | 0 |
| Jan 18, 2026 | 0 |
| Jan 11, 2026 | 0 |
| Jan 4, 2026 | 0 |
| Dec 28, 2025 | 0 |
| Dec 21, 2025 | 0 |
| Dec 14, 2025 | 0 |
| Dec 7, 2025 | 0 |
| Nov 30, 2025 | 0 |
| Nov 23, 2025 | 0 |
| Nov 16, 2025 | 0 |
| Nov 9, 2025 | 0 |
| Nov 2, 2025 | 0 |
| Oct 26, 2025 | 0 |
| Oct 19, 2025 | 0 |
| Oct 12, 2025 | 0 |
| Oct 5, 2025 | 0 |
| Sep 28, 2025 | 0 |
| Sep 21, 2025 | 0 |
| Sep 14, 2025 | 0 |
| Sep 7, 2025 | 0 |
Metrics updated Sep 1, 2026 · collected automatically from the GitHub API
Spec structure
- Location
.kiro/- Formats
- Markdown
- Notes
- Currently contains only
steering/(steering files); nospecs/directory remains on the default branch. Kiro's spec dogfooding is better observed in kirodotdev/Kiro, whose.kiro/specs/github-issue-automation/holdsrequirements.md,design.md, andtasks.md.
Assessment drift: high
Spec-to-code drift
High. The .kiro/ directory hasn’t changed since July 2025 while code development continued through July 2026,
and only steering files — not specs — remain in-tree. Whatever spec-driven process produced the game, its artifacts
are no longer maintained alongside the code.
Defects and rework
Not yet assessed.
Maintenance outcomes
A cautionary data point from a vendor’s own showcase: even a first-party demo can end up with abandoned spec artifacts once the launch push is over. It also illustrates a measurement gap this observatory has to live with — for closed-source tooling, in-tree artifacts are the only observable trace of the process, and they may not reflect how the team actually works day to day.
Timeline
-
Code development continues
Latest code commit, with .kiro/ untouched for over a year.
-
Last .kiro/ change
"Adding the right steering files to main" — the last time spec artifacts were touched.
-
Kiro artifacts introduced
First commit touching the .kiro/ directory.