solo-research
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
/research
Deep research before PRD generation. Produces a structured research.md with competitive analysis, user pain points, SEO/ASO keywords, naming/domain options, and market sizing.
Live Context
- Branch: !
git branch --show-current 2>/dev/null - Recent changes: !
git log --oneline -5 2>/dev/null
MCP Tools (use if available)
If MCP tools are available, prefer them over CLI:
kb_search(query, n_results)— search knowledge base for related docsweb_search(query, engines, include_raw_content)— web search with engine routingsession_search(query, project)— find how similar research was done beforeproject_info(name)— check project details and stackscodegraph_explain(project)— architecture overview of an existing project (stack, patterns, deps)codegraph_query(query)— raw Cypher queries against code graph (find shared packages, dependencies)project_code_search(query, project)— semantic search over project source code
More from fortunto2/solo-factory
solo-build
Use when "build it", "start building", "execute plan", "implement tasks", "ship it", track ID referenced, or plan tasks need execution. Do NOT use for planning (/plan) or scaffolding (/scaffold).
34solo-swarm
Use when "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or want faster multi-angle alternative to /research. Do NOT use for solo research (/research) or idea scoring (/validate).
34solo-humanize
Use when "humanize this", "make it sound human", "strip AI patterns", "clean up the copy", or text reads like AI-generated output with em dashes and stock phrases.
33solo-audit
Use when "audit KB", "check frontmatter", "find broken links", "tag cleanup", "knowledge base quality", or docs need health check. Do NOT use for SEO audits (/seo-audit) or code reviews (/review).
31solo-scaffold
Use when "scaffold project", "create new project", "start new app", "bootstrap project", "set up from PRD", or need project from PRD + stack template. Do NOT use for planning features (/plan) or PRD generation (/validate).
30solo-plan
Use when "plan this feature", "create implementation plan", "write a spec", "battle plan", describing a feature/bug/refactor, or need task breakdown before building. Do NOT use for idea validation (/validate) or execution (/build).
28