菜单
(forwward) Designs viral loops, referral systems, growth mechanics, and launch playbooks for product-led growth. Triggers on go-to-market strategy, viral mechanics, launch planning, growth metrics, K-factor, or referral programs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
(forwward) Runs lint, typecheck, build, and test in a self-healing loop that reads errors, fixes them, and retries up to 4 times. Triggers on verify, check, make sure it works, pre-commit validation, pre-deploy checks, or any quality gate.
(forwward) Ships code — owns the pipeline from verified branch to deployed and healthy. Stack-aware shipping engineer and on-call SRE: detects Node/Go/Python/Ruby/Rust/Java/Terraform/Pulumi/Lambda/CDK and runs the right gate, build, test, deploy. Three modes — PR, release (version bump, changelog, tag, health check), hotfix. Confirms before every irreversible step. Use for "ship this", "open a PR", "release", "deploy", "cut a release", "hotfix".
(forwward) Orchestrates multi-agent engineering and business teams by analyzing tasks, selecting team shapes, assigning specialist roles, and coordinating parallel agent work with skill dispatch. Triggers on tasks needing 2+ agents, feature dev with frontend + backend, quality audits, research sprints, bug hunts, or any work that benefits from parallel specialization.
(forwward) Consolidates recent team work — commits, PRs, decisions, fixes, learnings — into a shared `team-memory/MEMORY.md`. Like REM sleep for the team. Use after a PR merges, after a release, at sprint-end, or when the user says "team memory", "what did we ship this week". Reads git log, PRs, CHANGELOG, ADRs, and the conversation; appends Shipped, Decisions (with WHY), Fixes (root cause), Learnings, Open Threads. Not for one-off summaries or PII.
(forwward) Guides fullstack feature development with clean code patterns across any stack — TypeScript, Python, Go, Ruby, Java, Rust, and more. Detects the project's stack before advising. Triggers on implementing features, writing code, shipping UI + API + DB changes, or any hands-on engineering work.
(forwward) Onboards founders to forwward-teams by learning what they build, initializing the environment, and recommending which skills to use first. Triggers on first install, new project setup, getting started, or when a user asks what forwward-teams can do.
| name | gtm |
| description | (forwward) Designs viral loops, referral systems, growth mechanics, and launch playbooks for product-led growth. Triggers on go-to-market strategy, viral mechanics, launch planning, growth metrics, K-factor, or referral programs. |
Build products that spread themselves through authentic resonance, not gimmicks.
Product has network effects?
├─ Yes → Design embedded viral loop
│ ├─ Multi-party workflow? → Embedded loop (Calendly model)
│ ├─ Creates shareable output? → UGC loop (Canva model)
│ └─ Has visible usage? → Casual contact loop (Slack model)
└─ No → Evaluate referral program
├─ High LTV? → Two-sided incentive
├─ Community-driven? → Status/recognition rewards
└─ Transactional? → Reconsider if viral is right channel
K factor = users sharing × invites per share × conversion rate
| Loop Type | Typical K | Example |
|---|---|---|
| Embedded | 0.5–2.0 | Calendly, DocuSign |
| UGC | 0.3–1.0 | Canva, Loom |
| Community | 0.2–0.5 | Discord, Notion |
K > 1.0 = viral growth. K > 0.3 = meaningful organic boost.