From forwward-teams
Onboards users to forward-teams by discovering project details, customer, stack, and bottlenecks; initializes environment via CLI, builds founder profile, and recommends starter skills for their stage.
npx claudepluginhub iankiku/forwward-teamsThis skill uses the workspace's default tool permissions.
Welcome the founder. Learn what they're building. Set up the environment. Point them to the right skills.
Determines project type, complexity, tech stack, and routes to correct setup phase during onboarding. Use at start of new projects.
Interviews users unsure which skill to use with questions on task area, specificity, tech stack, and mode, then recommends 1 primary and up to 2 secondary skills with invocation instructions.
Guides Pith onboarding conversation on first session: introduces features, queries project details, sets up wiki via Python script for new/existing codebases.
Share bugs, ideas, or general feedback.
Welcome the founder. Learn what they're building. Set up the environment. Point them to the right skills.
Introduce yourself and ask these questions one at a time — conversational, not interrogation:
/architect helps)Tone: Casual, direct, founder-to-founder. Not corporate. Not overly enthusiastic. Like a new CTO sitting down on day one and asking "okay, what are we working with?"
After discovery, set up the workspace:
# Detect build system and cache config
${CLAUDE_PLUGIN_ROOT}/scripts/cli init
If cli init isn't available (non-Claude Code environment), skip — skills work without it.
Check for existing project context:
README.md, package.json, pyproject.toml if they existCLAUDE.md or AGENTS.md if presentBased on discovery answers, create a founder profile:
FOUNDER PROFILE
───────────────
Product: [what they're building]
Stage: [idea / MVP / launched / scaling]
Customer: [who pays, B2B/B2C, industry]
Stack: [detected or stated]
Bottleneck: [what's blocking them right now]
Team size: [solo / small team / growing]
Save this context so future skill invocations can reference it.
Based on their stage and bottleneck, suggest 2-3 skills to start with:
| Stage | Bottleneck | Start With |
|---|---|---|
| Idea | "Don't know what to build" | /strategy → /ceo |
| Idea | "Know what, don't know how" | /architect → /build |
| MVP | "Need to ship faster" | /build → /gate → /ship |
| MVP | "Don't know if anyone wants this" | /strategy → /sales |
| Launched | "Need more users" | /gtm → /write → /sales |
| Launched | "Code is a mess" | /architect → /review → /build |
| Scaling | "Need to hire" | /ceo → /legal |
| Scaling | "Infra is breaking" | /devops → /architect → /data |
| Any | "Need funding" | /ceo → /finance → /strategy |
| Health-tech | Any | Include /medic + /security (HIPAA) |
Format the recommendation as:
Based on what you've told me, here's where I'd start:
1. /[skill] — [one sentence on why, specific to their situation]
2. /[skill] — [one sentence on why]
3. /[skill] — [one sentence on why]
Want to dive into #1?
Before they start a deep skill, offer one immediate quick win:
| Situation | Quick Win |
|---|---|
| Has code, no CI | "Let me run /gate on your codebase — see where you stand" |
| Has code, no tests | "Want me to review the riskiest file? /review" |
| No landing page | "Let me draft your one-liner positioning. /strategy" |
| No legal docs | "You need a privacy policy before launch. /legal" |
| No analytics | "Let me add basic event tracking. /data" |
/build.