Menu

Spec first, then let it haunt you: building Deadline Séance with Kiro
📰

Spec first, then let it haunt you: building Deadline Séance with Kiro

DEV Community: typescript·Hugo Valer·about 10 hours ago
#t1XuBjxQ
#devtotypescript#devto#dev#kiro#rule
Reading 0:00
15s threshold

This post is written as part of the Kiroween 2026 hackathon.

The meeting nobody wants

Every release ends the same way. Monday morning, the freeze is Friday at six, and the board holds far more work than the team can do. Someone has to decide what gets cut, and it is usually the loudest voice in the room.

Deadline Séance turns that meeting into a rule you can see. Tickets that fit stay inside the safehouse; the rest are buried under tombstones with an epitaph that says why ("It needed 8 points; the night had 0 left"). Burn the candle down from Friday to Wednesday and capacity drops from 59 to 35 points. Send Ana away and the cut updates at once. Every decision goes into a chronicle you can undo.

Try it (no sign-in, nothing leaves your browser): https://hvaler.github.io/deadline-seance/

Writing the rule before the code

The whole product was built in Kiro IDE: specs, steering, a hook and the MCP server all live in its .kiro folder.

The first thing I put into Kiro's steering was not a style guide.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.