القائمة
Coordinates the full startup idea pipeline from brainstorm to investor outreach. Use when the user starts a new idea project, asks for the 'full pipeline', or references stages/gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate complete service-level Terraform infrastructure with modules, environments, and CI/CD. Use when adding Terraform to a new service or bootstrapping infrastructure from scratch.
Audit JS/TS projects against NPM Security Guidelines covering project setup, dependency hygiene, CI/CD pipeline, Dependabot, and incident response. Use when reviewing package.json or lockfiles, adding or upgrading npm dependencies, setting up CI security gates, hardening a new repo, or responding to a compromised package.
Creates FastAPI endpoints with layered architecture (Router → Service → Repository). Use when creating new API endpoints, CRUD operations, or scaffolding a new domain module in a FastAPI project.
Python/FastAPI coding standards including async patterns, Pydantic v2, SQLAlchemy 2.0, and project structure. Use when writing Python code, reviewing FastAPI projects, or learning FastAPI conventions.
Testing patterns for FastAPI with pytest-asyncio, httpx AsyncClient, fixtures, and test data factories. Use when writing tests, setting up test infrastructure, or improving coverage in a FastAPI project.
Investigate a monitoring alert end-to-end. Pulls metrics, logs, traces, and recent code changes to identify root cause. Works with any monitoring MCP.
| name | startup-pipeline |
| description | Coordinates the full startup idea pipeline from brainstorm to investor outreach. Use when the user starts a new idea project, asks for the 'full pipeline', or references stages/gates. |
| allowed_tools | ["WebSearch","Read"] |
The full flow for taking an idea from zero to investor-ready.
STAGE 1: DISCOVER STAGE 2: FILTER STAGE 3: DIG STAGE 4: BUILD
───────────────── ─────────────── ───────────── ──────────────
/brainstorm /validate /research /pitch
/teardown /outreach
/content
Generate ideas ──► Kill bad ones fast ──► Go deep on survivors ──► Make materials
8-15 ideas GO / TEST / PASS Market + competitors Deck, memo, emails
Pick top 3 Need data? Move on Real numbers Ready to send
📁 01-brainstorm/ 📁 03-validation/ 📁 02-research/ 📁 04-build/
On first run, check for a config.json in the project root. If it doesn't exist, ask the user and create one:
{
"projectName": "my-idea",
"outputDir": "projects/my-idea",
"defaultAudience": "B2B SaaS founders",
"fundingGoal": "bootstrap",
"currentStage": 1
}
Update currentStage as the user progresses through gates. This lets the pipeline resume across sessions.
Each stage has a gate. Don't move forward unless you pass.
After brainstorm, you need at least 1 idea where:
If none pass → brainstorm again or pick a new space.
After validation, you need:
If PASS → stop here. Move to next idea. If TEST MORE → do one cheap test first, then re-validate.
After deep research, you need:
If no → archive the project. Save the research for later.
After pitch materials, check:
Each stage saves files with a prefix so they stay sorted:
projects/my-idea/
├── 01-brainstorm/
│ └── brainstorm-session-2026-03-02.md
├── 02-research/
│ ├── market-research-2026-03-03.md
│ ├── teardown-competitor-a-2026-03-03.md
│ └── teardown-competitor-b-2026-03-03.md
├── 03-validation/
│ └── validation-report-2026-03-02.md
├── 04-build/
│ ├── pitch-deck-outline-2026-03-04.md
│ ├── one-pager-2026-03-04.md
│ └── investor-emails-2026-03-04.md
└── README.md
| Combo | Stages | What happens |
|---|---|---|
/kickoff [theme] | 1 → 2 | Brainstorm + validate top ideas |
/deep-dive [project] | 3 | Research + teardown competitors |
/fundraise [project] | 4 | Pitch materials + outreach drafts |
/startup [theme] | 1 → 2 → 3 → 4 | Everything, with pauses at each gate |
No BS. Honest feedback only.
This is a two-way talk:
When I ask you a question, I always:
When you ask me something:
Never: