<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: jason-1991</title>
    <description>The latest articles on DEV Community by jason-1991 (@jason1991).</description>
    <link>https://dev.to/jason1991</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257136%2Fec360614-fae3-4996-a565-db53b6116b15.png</url>
      <title>DEV Community: jason-1991</title>
      <link>https://dev.to/jason1991</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jason1991"/>
    <language>en</language>
    <item>
      <title>Building Deadline Dungeon with Kiro: Specs First, Code Second — and One Very Stubborn Boss</title>
      <dc:creator>jason-1991</dc:creator>
      <pubDate>Sat, 21 Nov 2026 10:29:37 +0000</pubDate>
      <link>https://dev.to/jason1991/building-deadline-dungeon-with-kiro-specs-first-code-second-and-one-very-stubborn-boss-39d3</link>
      <guid>https://dev.to/jason1991/building-deadline-dungeon-with-kiro-specs-first-code-second-and-one-very-stubborn-boss-39d3</guid>
      <description>&lt;p&gt;&lt;em&gt;This post was written as part of the Kiroween 2026 hackathon, where Deadline Dungeon is entered in the Costume Contest. Play it here: &lt;a href="https://jason-1991.github.io/deadline-dungeon/" rel="noopener noreferrer"&gt;https://jason-1991.github.io/deadline-dungeon/&lt;/a&gt; · Code: &lt;a href="https://github.com/jason-1991/deadline-dungeon" rel="noopener noreferrer"&gt;https://github.com/jason-1991/deadline-dungeon&lt;/a&gt; · Devpost: &lt;a href="https://devpost.com/software/deadline-dungeon-h0amqn" rel="noopener noreferrer"&gt;https://devpost.com/software/deadline-dungeon-h0amqn&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Every hackathon ends the same way: a wall of unfinished tasks and a deadline that feels like a final boss. So for Kiroween, I built the game I was already living in. &lt;strong&gt;Deadline Dungeon&lt;/strong&gt; turns a project plan into a dungeon crawler: milestones become rooms, tasks become monsters, and the deadline itself is the Boss. Its HP is the sum of all your remaining work. You fight it with a focus timer — one focused minute, one point of damage.&lt;/p&gt;

&lt;p&gt;The game is the fun part. This post is about how it was built: entirely spec-first in Kiro, with the evidence chain committed to the repo under &lt;code&gt;/.kiro&lt;/code&gt;. That includes the part where my development environment fell over mid-hackathon and the whole project had to emigrate to a server in Sydney.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcxf7et48bci7xtihz72h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcxf7et48bci7xtihz72h.png" alt="The dungeon map: rooms, monsters, and the Deadline Boss" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Step zero: specs before code
&lt;/h2&gt;

&lt;p&gt;Kiro's spec workflow gives every feature three documents — &lt;code&gt;requirements.md&lt;/code&gt;, &lt;code&gt;design.md&lt;/code&gt;, and &lt;code&gt;tasks.md&lt;/code&gt; — and I made a rule for this project: nothing in the game layer gets written off-spec. Deadline Dungeon has four features, so the repo carries four spec trios:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;dungeon-creation&lt;/code&gt; — forging a dungeon from a project name, deadline, milestones, and tasks&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;focus-combat&lt;/code&gt; — the timer, damage, XP, levels, and streaks&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;boss-settlement&lt;/code&gt; — the Boss bar, victory/defeat, deadline extension&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;report-card&lt;/code&gt; — the shareable 1200×630 report card and the badge shelf&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Implementation followed the task lists item by item. That sounds bureaucratic until the first time you come back to a session after a break and the tasks file tells you exactly where you stopped. During a hackathon, "where was I?" is a real boss too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Steering docs: the rules live in the repo, not in chat
&lt;/h2&gt;

&lt;p&gt;The single most useful habit this project taught me: &lt;strong&gt;if a rule matters, it goes into a steering doc, not into a chat message.&lt;/strong&gt; Chat scrolls away; steering docs are loaded every session.&lt;/p&gt;

&lt;p&gt;Two steering files ran this project. &lt;code&gt;tech-rules.md&lt;/code&gt; set the engineering contract: all game logic as pure functions in &lt;code&gt;src/game/&lt;/code&gt;, localStorage only, no backend, and components kept small. &lt;code&gt;product-rules.md&lt;/code&gt; locked the game math, under a header I enjoyed writing more than I should admit:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Game balance (locked unless the balance agent proposes and a human approves)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Under it are the numbers that define the game: monster HP is stored in focus-minutes (estimated hours × 60), one focused minute equals one point of damage, the level curve is 50 × n × (n−1) / 2 cumulative XP — and the invariant the whole design hangs on:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Boss HP is always derived (sum of monster HP), never stored separately.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That one line is why the Boss can never lie to you. There is no boss-HP variable to drift out of sync; there is only the work that's left.&lt;/p&gt;

&lt;p&gt;Steering also caught a real bug. During the polish pass, a review against &lt;code&gt;product-rules.md&lt;/code&gt; found the combat code awarding XP only on kills. The steering doc says XP equals damage actually applied, with overkill truncated. The code was wrong, the doc was right, and the fix — plus four new tests pinning the rule down — shipped in the same session. Specs aren't documentation you write after the fact; on a good day, they're the referee.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hooks and property-based tests: trust, but verify automatically
&lt;/h2&gt;

&lt;p&gt;Two agent hooks in &lt;code&gt;/.kiro/hooks&lt;/code&gt; rerun the logic tests and the typecheck when game files are saved. They're boring, and that's the point: a broken invariant should fail in seconds, not at demo time.&lt;/p&gt;

&lt;p&gt;The game math is verified with &lt;strong&gt;property-based tests&lt;/strong&gt; (fast-check), not just examples. The properties that matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Damage never makes HP negative.&lt;/li&gt;
&lt;li&gt;XP is conserved: you earn exactly the damage you applied, never the overkill.&lt;/li&gt;
&lt;li&gt;Across random sequences of hits, Boss HP always equals the total remaining monster HP.&lt;/li&gt;
&lt;li&gt;A badge is never awarded twice.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The suite ended up with 29 tests, all green. Example tests check the cases you thought of; properties check the ones you didn't — and in a game where every number is derived from every other number, the second kind earns its keep.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjuqmz61mow04zgmqgadi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjuqmz61mow04zgmqgadi.png" alt="Focus combat, the badge shelf, and a freshly earned badge" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The night the toolchain moved to Sydney
&lt;/h2&gt;

&lt;p&gt;Mid-hackathon, my local Kiro CLI setup developed a very specific failure: it could read, but write operations kept dying with connection resets. Stage 1 and the Stage 2 logic layer were already committed, but the build could not continue with a toolchain that dropped every third file write.&lt;/p&gt;

&lt;p&gt;So the project emigrated. I cloned the repo onto a small ARM cloud instance in Sydney, installed Kiro CLI there, signed in, and ran every remaining stage through Kiro on that box — Stage 2 UI, Stage 3 focus combat, Stage 4 boss settlement, and both polish rounds. Every change was pulled back to my machine and re-verified locally (typecheck, tests, production build) before it was pushed.&lt;/p&gt;

&lt;p&gt;Here's the part that made this painless instead of terrifying: &lt;strong&gt;the specs and steering docs were in the repo.&lt;/strong&gt; The new environment didn't need my chat history, my memory, or my intentions. It needed &lt;code&gt;/.kiro&lt;/code&gt; — and &lt;code&gt;/.kiro&lt;/code&gt; was complete. Spec-driven development is usually sold as a quality practice. That night, it turned out to be a disaster-recovery practice.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vibe where it belongs
&lt;/h2&gt;

&lt;p&gt;By design, not everything was spec-driven. The theme CSS, layout sketches, and the "spooky-cute" art direction (a pumpkin-and-ghost costume wrapped around a productivity tool — it is a Costume Contest, after all) were vibe-coded in conversation. The split was the point: &lt;strong&gt;the rules of the game are a contract; the look of the game is a conversation.&lt;/strong&gt; Kiro handled both modes, but only one of them got a steering doc and a property test.&lt;/p&gt;

&lt;h2&gt;
  
  
  The demo dungeon is the submission itself
&lt;/h2&gt;

&lt;p&gt;For the demo video, I forged a dungeon out of the actual submission plan — rooms for Idea &amp;amp; Setup, Build, and Ship; monsters for the core feature, the polish pass, the demo prep, and the submission itself. Beating the Boss meant shipping the game. The victory report card in the video is real:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp9bgm640evyjicke8qlu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp9bgm640evyjicke8qlu.png" alt="The victory report card" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Deadline Dungeon was submitted to Kiroween 2026 on November 21 — twelve days before the deadline. Somewhere, a Boss is still annoyed about that.&lt;/p&gt;

&lt;p&gt;If you take one thing from this build, take the steering habit: write the rule down where the agent will read it every session. Your future self — possibly on a different continent's server — will thank you.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Deadline Dungeon — play it: &lt;a href="https://jason-1991.github.io/deadline-dungeon/" rel="noopener noreferrer"&gt;https://jason-1991.github.io/deadline-dungeon/&lt;/a&gt; · GitHub (MIT, &lt;code&gt;/.kiro&lt;/code&gt; included): &lt;a href="https://github.com/jason-1991/deadline-dungeon" rel="noopener noreferrer"&gt;https://github.com/jason-1991/deadline-dungeon&lt;/a&gt; · Devpost project: &lt;a href="https://devpost.com/software/deadline-dungeon-h0amqn" rel="noopener noreferrer"&gt;https://devpost.com/software/deadline-dungeon-h0amqn&lt;/a&gt; · Built with Kiro for the Kiroween 2026 hackathon.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kiro</category>
      <category>ai</category>
      <category>gamedev</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
