saas-dev-flow

Orchestrates a seven-stage SaaS development workflow from requirement triage to versioned deployment.

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/luce12/agent-dev-workflow --skill saas-dev-flow-luce12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: saas-dev-flow
Source: https://github.com/luce12/agent-dev-workflow/tree/main/skills/saas-dev-flow
Command: npx skills add https://github.com/luce12/agent-dev-workflow --skill saas-dev-flow-luce12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping SaaS features, redesigns, or bug fixes without a disciplined process leads to broken releases, security gaps, and inconsistent UI. This Skill turns any product request into a verified release by enforcing a seven-stage workflow with hard gates at every step. ## Core Features & Use Cases - Seven gated stages: requirement triage, brand design, development, automated tests, real-browser verification, security audit, and versioned deployment — no stage can be skipped. - Toolkit orchestration: coordinates companion skills for design (hallmark, impeccable, design-audit), browser testing (playwright), security auditing, and GSAP motion specs. - Printable release checklist: a references/checklist.md file covering every gate, from zero console errors to database backups named by old version. - Use Case: Ask the agent to build a new inspection module for your SaaS; it will confirm the plan, design with tokens, write backend migrations and permissioned routes, run tests, verify in a real browser at mobile widths, audit security, and deploy with a versioned database backup. ## Quick Start Build the new reporting module using the saas-dev-flow workflow and do not release until every gate passes.

Frequently Asked Questions about saas-dev-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ship a SaaS feature without breaking existing behavior?▼

Follow the seven-stage workflow: triage the requirement, develop backend-first with permissioned routes, run the full test suite, verify in a real browser with Playwright, audit security, then deploy with a version bump and a database backup named by the old version.

What workflow should I use for a full SaaS rebrand?▼

Use the brand design stage: invoke the hallmark toolkit for the landing page, build with named design tokens across brand, marketing, and business layers, then gate the result with the impeccable or design-audit toolkits before any development begins.

Does this workflow require Playwright for browser testing?▼

Yes, stage five invokes the playwright toolkit or equivalent browser automation to walk every page, confirm zero console errors, check mobile widths at 320/375/414/768px, and test new features end-to-end before release.

What security checks happen before a production deployment?▼

Stage six runs the codex-security-audit-skill covering secrets in environment variables only, auth on protected routes, file upload whitelists with random filenames, login rate limiting, security headers like HSTS, and server hardening with fail2ban or a firewall.

When should I not use this SaaS workflow?▼

Skip it for single-step tasks like answering a code question or making a trivial copy change. The workflow is designed for complete releases — new modules, restyles, or bug-fix shipments — where skipping a gate has real production risk.