Build a whole product
From one sentence to shipped slices, with your rules in the repository from the first commit.
YouBuild a SaaS where clinics track no-shows. Make it perfect and ship it this week.
plan.md
Plan: Tallyroom
Now at: phase 1, gate 1
Who: front-desk staff at small clinics
Slice 1: import → remind → confirmations
SMS consent: UNKNOWN
- 0 Rules
- 1 Frame · waiting on you
- 2 Map
- 3 Design system
YouBuild a SaaS where clinics track no-shows. Make it perfect and ship it this week.
Plan · Tallyroom
- PROVIDEDThe users are front-desk staff at small clinics (your request).
- INFERREDSlice 1 is the core loop: import today’s list, send reminders, see who confirmed.
- UNKNOWNWhether the clinic’s consent covers SMS reminders. A legal question the plan can’t settle.
- GATEGate 1 is open until you approve the brief and what v1 is not.
Your callApprove the brief, or change it.
Illustrative example. The labels: PROVIDEDYour data or research says soINFERREDA hunch, with how to test itUNKNOWNCan’t tell; says what would settle itGATEWaits on your decision before the next phase
Say it your way
- “Build me a SaaS for small gyms to manage class bookings.”
- “Set up this repo so every agent follows our UX rules.”
- “Plan the whole app before anyone writes code.”
It works through
- Rules
- Frame
- Map
- Design
- Build
- Verify
- You decide
You get back
- Rules in your repository
- A plan with gates
- Slices, core loop first
- Every promise tracked
Install in one command.
It loads by itself when a request like these comes in. Free and open source, no account.
Claude Code
unzip splitfire-platform-build.zip -d ~/.claude/skills/ Every project on this machine. Use .claude/skills/ inside a repository to share with your team.
Codex
unzip splitfire-platform-build.zip -d ~/.agents/skills/ Every project. Use .agents/skills/ inside a repository instead, then restart Codex.
Claude apps
On claude.ai or the desktop app, upload the .zip in your skills settings. One zip is one skill.