SaaS Feature Planner FAQs

Question 1

How does it understand my current project structure?

Accepted Answer

It utilizes tools like Grep, Glob, and Read to explore your repository, identifying existing patterns, components, and utilities to ensure the new feature plan is cohesive.

Question 2

Can I use the output with the /dev command?

Accepted Answer

Yes, the plan is formatted as a structured Markdown spec specifically designed to be easily interpreted and executed by the /dev command or other AI coding tools.

Question 3

Does the plan-feature skill write actual code?

Accepted Answer

No, this is a planning-only skill designed to create a detailed technical specification and roadmap that can be subsequently used by coding tools or developers.

Question 4

What SaaS-specific aspects does it analyze?

Accepted Answer

The skill specifically focuses on multi-tenancy (RLS policies), subscription tier gating, billing impacts (Stripe), and organizational scoping to ensure features are production-ready for SaaS.

Question 5

What is included in the phased implementation plan?

Accepted Answer

The output includes an overview, a four-phase task list (Foundation, Core Logic, UI/Integration, Polish), a SaaS readiness checklist, and a section for risks and open questions.

SaaS Feature Planner

Key Features

Use Cases

SaaS Feature Planner

Key Features

Use Cases