startup-team

Orchestrates nine functional team skills to evaluate, sequence, and prioritize venture work in the Nigerian market.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill startup-team-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: startup-team
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/startup-team
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill startup-team-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Solo founders juggling multiple ventures often skip the market-level gut check, spread effort evenly across ventures, or mistake a finished build for launch readiness. This Skill sits above nine functional team skills (product, ui-ux, dev, security, sales, content, legal, finance, ops) and answers the venture-level questions: is this idea worth building, which teams engage in what order, where should this week's focus go, and are we actually ready for a milestone. ## Core Features & Use Cases - Opportunity evaluation (/opportunity): Assesses a new idea against the Nigerian market — problem quality, evidence ladder, bottom-up sizing, competition, why-now — and returns a pursue now / later / don't call before any functional team spends effort. - Cross-team orchestration (/orchestrate): Sequences which of the nine functional teams engage at each venture stage, distinguishing cheap-anytime hygiene (IP assignment, secrets hygiene) from stage-gated work (financial models, compliance audits). - Portfolio focus and readiness (/focus, /status, /readiness): Triage across multiple live ventures, name the single biggest constraint, and run go/no-go checks for launches, raises, or Startup Label applications. - Use Case: A founder asks "should I even bother with this idea?" — the Skill runs /opportunity, grounds the sizing in current naira exchange rates and funding climate, and either hands off to product-team's /idea or states plainly why not. ## Quick Start Ask the startup team to evaluate whether your new venture idea is worth pursuing in the current Nigerian market before committing any build effort.

Frequently Asked Questions about startup-team

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

FAQPage Schema
How do I evaluate whether a startup idea is worth pursuing in Nigeria?

Use the /opportunity command to run a market-level gut check covering problem quality, evidence strength, bottom-up addressable sizing, competition, and why-now timing. It returns a pursue now, pursue later, or don't pursue call with the specific condition that would flip the decision.

How do I sequence product, design, dev, and legal work for a new venture?

Use the /orchestrate command with your goal, such as launching V1 or raising a seed round. It sequences which of the nine functional teams engage at each stage and separates cheap-anytime hygiene like IP assignment from stage-gated work like financial models.

How do I decide which of my ventures deserves focus this week?

Use the /focus command for portfolio-level triage across live ventures. It weighs time-sensitivity, path to the next milestone, and cost of neglect, then names which venture gets primary attention and which are explicitly deprioritized.

What does a fundraising readiness check actually cover?

The /readiness command for a raise checks the six questions investors actually ask, whether evidence matches the venture's real stage, the weakest risk category, the concreteness of the ask, and the fallback if the round does not close. It also verifies data-room and diligence readiness.

Does this skill replace product, dev, or legal team skills?

No, it routes and sequences rather than replacing them. It decides what needs to happen and in what order, then hands the actual deliverable work to the named functional team skill that owns that discipline.

When should I not use venture-level orchestration?

Skip it when a request is really one discipline's work, such as writing a spec, drafting a contract, or building a feature. Route those directly to the owning functional team skill instead of producing a shallower version at the orchestration layer.