app-lifecycle tells an agent which stage a SaaS product is in and what finishing it means. The stages run from a brief and screen options through design, screens on sample data, setup, a first real slice, browser proof, publish, the front door, go-live and every release after.
Each stage names its output, the evidence that closes it and the skills that hold the how. The owner keeps product, design, legal text and release decisions; the agent proposes, builds and supplies evidence.
What You Get
- An eleven-stage table with what each stage produces and when it is done, from brief to every release after go-live
- A suggested three-phase grouping with closing states, and rules for phase previews that never block coding
- Rules that hold at every stage: tests and docs land with the change, coordinator evidence closes a stage, deploying pushes are reviewed
- Shape declarations and what each skips, default choices with reopen triggers, a capabilities list for what comes next, and templates for the product section, brief, plan, decision log and stage brief
- A list of the dashboard steps only the owner can click at setup, publish, front door and go-live
Common Use Cases
- Asking ‘where are we’ on a SaaS build and getting the stage and its missing evidence
- Planning phases and a review cadence before building starts
- Deciding what to defer and what to propose next after the first release
- Setting the shape of a new product before any screen is built
What Makes It Unique
Stages are checked against code, deploys and the gate, with status lines treated as claims. It orders work by visible value against cost, builds the front door early, and declines to design for rare cases unless they cross a line such as lost data, a leaked secret, the wrong environment or money. Owner decisions are exclusive, while owner previews stay open without blocking the next phase.
Under The Hood
The skill is markdown with a receipts file and reference files, and it ships no scripts. It describes the work an agent does with other skills: writing plan and decision documents, building screens, running tests, setting up a database and identity provider, deploying and promoting to production. The skill itself only reads the repository and writes planning documents. The vendor mechanisms in it use Next.js, Supabase, Clerk and Netlify, and the stage principles carry to other stacks.