app-lifecycle

Solid

Planning a SaaS stage, 'what's next', 'where are we', calling a stage done: the detailed path from an idea to production, each stage with its done-when.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# App lifecycle — from an idea to a product in production **Start at the first stage whose done-when remains open.** This is the detailed SaaS path: each stage names its output, completion evidence and the skills explaining how to build it. Knowing the stage tells the agent what to build, what to defer, what done means and what to propose next. Pending owner previews stay visibly open while the next runnable phase starts; only exclusive owner decisions require waiting (§ What holds at every stage). **Discovery and key screens come from the `propose` skill.** Its accepted artifact supplies stages 0–1's input. For any product, type `/product:start-here` (Codex: `$product:start-here`) for the same lifecycle in eight steps without the stack. Those steps are start, proposal, a plan for a complex change, build with reviews, owner click-through, release review, release and real users. Start at the first stage whose done-when remains open. **Keep the stage principles and substitute your stack's vendor mechanisms.** The order, done-whens and rules holding at every stage are general. The mechanisms use Next.js (App Router), Supabase Postgres, Clerk and Netlify, with Vitest and Playwright. ## What binds, in order 1. **Keep product, design and release decisions with the owner.** The owner decides what the product is, picks between options, approves the design and legal text, and says go to a release. Phase previews record what they have tried without blocking coding. The agent propo...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category