Project Discovery — Archetype Router
You take an idea and produce EVERYTHING needed to build it. The archetype flag determines which discovery flow to run.
Arguments: $ARGUMENTS
--saas <idea> = SaaS product (public, billing, landing page, SEO)
--internal <idea> = Internal tool (team-only, SSO, no billing, no landing page)
--client <idea> = Client project (built for someone else, their branding, handoff)
--resume = resume from where we left off (reads archetype from idea-brief.md)
--tools-only = skip discovery, just research tools from existing external-tools.md
--refresh = re-research tools (update existing docs)
Routing
If --resume: Read dev/active/discovery/idea-brief.md, extract ## Archetype: line, load the matching flow.
If --tools-only or --refresh: These are archetype-agnostic — skip to tool docs phase. See saas-flow.md for the tool docs pipeline (same for all archetypes).
Otherwise: The flag is REQUIRED. If no flag is provided, ask:
"What type of project is this?"
- SaaS — public product with billing, landing page, SEO
- Internal tool — team-only, SSO/auth, no billing, no public pages
- Client project — built for someone else, their branding, delivered to them
Then route to the matching flow.
Flow Files
| Archetype |
Flow |
Description |
--saas |
references/saas-flow.md |
Full SaaS discovery: 4 research agents, 5 personas, 7 docs, discovery critics (discovery-critic + ux-critic), tool validation, deep tool docs |
--internal |
references/internal-flow.md |
Scoped internal tool: 1 research agent, 3 personas, 4-5 docs, discovery critic only, tool docs if needed |
--client |
references/client-flow.md |
Client project: 2 research agents, 4 personas, 6-7 docs, discovery critic only, tool docs, handoff plan |
After routing: Read the flow file and follow it exactly. The flow file IS the complete instructions.
Shared References
All flows use these shared assets from references/project-discovery/:
library/skills/discover/references/project-discovery/agents/team-roster.csv — persona definitions
library/skills/discover/references/project-discovery/references/question-frameworks.md — question patterns
library/skills/discover/references/project-discovery/references/feature-inventory.md — feature categories
library/skills/discover/references/project-discovery/references/output-templates.md — doc templates
Idea Brief
All flows write dev/active/discovery/idea-brief.md with an ## Archetype: line:
# Idea Brief
## Archetype: {saas|internal|client}
## What: {1-2 sentences}
## Who: {target user}
## Reference: {app name + URL if available}
## Angle: {what's different}
## Open Questions: {research should answer these}
Critics Per Archetype
| Critic |
SaaS |
Internal |
Client |
| discovery-critic |
yes |
yes |
yes |
| ux-critic |
yes |
no |
no |
The discovery-critic (structural integrity) runs for ALL archetypes — every project needs complete, consistent, feasible docs.
The ux-critic (monetization UX, gating, upgrade flows, conversion) runs for SaaS ONLY — internal tools and client projects don't have billing/monetization/public conversion flows.
Each flow file specifies which critics to spawn at Phase 3e.
1---2name: discover3description: >4 Full project discovery. Archetype-aware — runs the right flow for SaaS, internal tools, or client projects.5 Produces docs/project/ + docs/tools/. Everything /mvp-spec needs.6 Use for "discover", "new project", "research idea", "scope project", "scope tool".7metadata:8 source: https://skillmd.com/skills/dabhiram13/discover9---1011# Project Discovery — Archetype Router1213You take an idea and produce EVERYTHING needed to build it. The archetype flag determines which discovery flow to run.1415Arguments: `$ARGUMENTS`16- `--saas <idea>` = SaaS product (public, billing, landing page, SEO)17- `--internal <idea>` = Internal tool (team-only, SSO, no billing, no landing page)18- `--client <idea>` = Client project (built for someone else, their branding, handoff)19- `--resume` = resume from where we left off (reads archetype from idea-brief.md)20- `--tools-only` = skip discovery, just research tools from existing external-tools.md21- `--refresh` = re-research tools (update existing docs)2223## Routing2425**If `--resume`:** Read `dev/active/discovery/idea-brief.md`, extract `## Archetype:` line, load the matching flow.2627**If `--tools-only` or `--refresh`:** These are archetype-agnostic — skip to tool docs phase. See saas-flow.md for the tool docs pipeline (same for all archetypes).2829**Otherwise:** The flag is REQUIRED. If no flag is provided, ask:3031> "What type of project is this?"32> 1. **SaaS** — public product with billing, landing page, SEO33> 2. **Internal tool** — team-only, SSO/auth, no billing, no public pages34> 3. **Client project** — built for someone else, their branding, delivered to them3536Then route to the matching flow.3738## Flow Files3940| Archetype | Flow | Description |41|-----------|------|-------------|42| `--saas` | `references/saas-flow.md` | Full SaaS discovery: 4 research agents, 5 personas, 7 docs, discovery critics (discovery-critic + ux-critic), tool validation, deep tool docs |43| `--internal` | `references/internal-flow.md` | Scoped internal tool: 1 research agent, 3 personas, 4-5 docs, discovery critic only, tool docs if needed |44| `--client` | `references/client-flow.md` | Client project: 2 research agents, 4 personas, 6-7 docs, discovery critic only, tool docs, handoff plan |4546**After routing:** Read the flow file and follow it exactly. The flow file IS the complete instructions.4748## Shared References4950All flows use these shared assets from `references/project-discovery/`:51- `library/skills/discover/references/project-discovery/agents/team-roster.csv` — persona definitions52- `library/skills/discover/references/project-discovery/references/question-frameworks.md` — question patterns53- `library/skills/discover/references/project-discovery/references/feature-inventory.md` — feature categories54- `library/skills/discover/references/project-discovery/references/output-templates.md` — doc templates5556## Idea Brief5758All flows write `dev/active/discovery/idea-brief.md` with an `## Archetype:` line:5960```markdown61# Idea Brief62## Archetype: {saas|internal|client}63## What: {1-2 sentences}64## Who: {target user}65## Reference: {app name + URL if available}66## Angle: {what's different}67## Open Questions: {research should answer these}68```6970## Critics Per Archetype7172| Critic | SaaS | Internal | Client |73|--------|------|----------|--------|74| discovery-critic | yes | yes | yes |75| ux-critic | yes | no | no |7677The **discovery-critic** (structural integrity) runs for ALL archetypes — every project needs complete, consistent, feasible docs.7879The **ux-critic** (monetization UX, gating, upgrade flows, conversion) runs for SaaS ONLY — internal tools and client projects don't have billing/monetization/public conversion flows.8081Each flow file specifies which critics to spawn at Phase 3e.