Skip to content
SkillModel-led5,283 tokens in use

app-lifecycle

The detailed SaaS path from idea to production: eleven stages, each with its output and a done-when, grouped into phases the owner can try, with shape switches and owner decisions.

680 stars on the repository MIT Licensephuryn/product-engineering · app-stack/skills/app-lifecycle
claude plugin install app-stack@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing app-lifecycle costs

42tokens idle
5,283tokens in use
32,319tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples3/15
  • Output15/15
  • Size11/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers