forwward-teams

(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.

(forwward) Aggressively audits and cleans a codebase — removes slop, dead code, and AI-generated noise; fixes DRY/SOLID violations; restructures toward the simplest correct implementation. One commit, no behavior changes. Use when the user says "audit the code", "clean up tech debt", "remove dead code", "deslop", "this codebase is a mess", or asks for a code-quality pass. Detects stack and applies idiomatic patterns. Works on full codebase or specific paths.

(forwward) Structures slide content for pitches, QBRs, board updates, investor updates, strategy decks, and all-hands. Produces slide-by-slide outlines with titles, talking points, and key data per slide — content, not visual design. Use when the user says "help me build a deck", "pitch deck", "QBR", "board update", "what slides do I need", or is preparing a high-stakes presentation without structure yet.

(forwward) Writes hiring artifacts — job descriptions, interview rubrics, scorecards, structured questions, and offer letter templates. Use when the user says "write a JD", "interview questions for", "hiring rubric", "scorecard", "offer letter", "hiring process", or describes a role they need to fill (even without saying "hire"). Works for any role: technical or non-technical, IC or leadership, FT or contractor.

(forwward) Turns transcripts, rough notes, or voice memos into a clean summary with decisions, action items (owner + deadline), and open questions. Use when the user pastes unstructured notes or asks "summarize this meeting", "meeting notes", "what were the action items", "write up from this call", "debrief", "what did we decide". Works for any meeting type — standups, 1:1s, client calls, all-hands, retrospectives.

(forwward) Writes operational artifacts for non-technical and cross-functional teams — SOPs, process docs, runbooks, workflow guides, handoff and escalation docs. Use when the user says "write an SOP", "document this process", "create a runbook", "how do we handle", "onboarding doc", "escalation process", or describes a repeatable workflow they want written down. Works for CS, ops, finance, HR, sales, support.

(forwward) Writes outcome-first status updates leaders actually read, with options + lean recommendation for blockers. Use when the user says "standup", "status report", "progress update", "weekly update", "executive summary", "update on [project]", or pastes project details without specifying intent. Reads git log, open PRs, tracker state, and the team-memory/ directory. Not for PRDs, postmortems, or peer engineering discussion.

(forwward) Designs system architecture, selects databases, structures projects, plans APIs, and defines caching strategies with scale-appropriate defaults. Triggers on system design, database selection, project structure, tech stack, API design, caching, or codebase organization.

(forwward) Configures CI/CD pipelines, Docker, monitoring, alerting, and infrastructure with reliability-first defaults. Triggers on CI/CD, Docker, deployment, monitoring, alerting, infrastructure setup, or production debugging.

(forwward) Performs paranoid code review checking trust boundaries, data integrity, performance, race conditions, error handling, and OWASP security. Triggers on code review, pre-merge checks, security audit, bug hunting, or any request to review, audit, or check code quality.

(forwward) Implements authentication, authorization, encryption, HIPAA compliance, SOC 2 controls, and security hardening with defense-in-depth defaults. Triggers on auth, encryption, compliance, penetration testing, privacy, or any security concern.

(forwward) Provides CEO-level strategic leadership frameworks for vision, OKRs, hiring, fundraising, resource allocation, and pivot decisions. Triggers on company strategy, growth direction, team scaling, investor relations, or any high-level business decision.

(forwward) Delivers technical strategy for architecture decisions, build-vs-buy analysis, tech stack selection, tech debt prioritization, and PRD writing. Triggers on architecture choices, technology evaluation, technical planning, or any CTO-level leadership question.

(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.

(forwward) Enforces anti-slop UI/UX standards with deliberate choices for color, typography, layout, and components — fights generic AI aesthetics. Triggers on UI/UX decisions, component design, color choices, layouts, typography, or visual design review.

(forwward) Models unit economics, burn rate, projections, pricing, and revenue forecasting with startup-specific frameworks. Triggers on CAC, LTV, burn rate, runway, pricing analysis, financial models, or any CFO-level financial question.

(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.

(forwward) Drafts terms of service, privacy policies, contracts, IP assignments, and open source licensing after gathering industry and jurisdictional context. Triggers on legal documents, terms, privacy policies, contracts, compliance, licensing, or any legal drafting need.

(forwward) Interprets medical records, clinical notes, FHIR data, and advises on medical data UI with OCR interpretation, clinical summarization, and drug interaction flags. Triggers on patient records, clinical data, medical PDFs, health-tech products, or medical data presentation.

(forwward) Configures a new AI agent through 10 discovery questions, creates platform-specific config files (Claude Code, Codex, Antigravity, Cursor, OpenClaw), tests integrations, and sets security guardrails. Triggers on setting up a new AI agent, configuring a workspace, or initializing agent context.

(forwward) Creates high-conversion landing pages, emails, and social posts using the Dual-PCP (Perception-Context-Permission) framework that resonates rather than directs. Triggers on landing pages, conversion copy, email sequences, ICP targeting, copy audits, perception shifting, micro-compliance, or SEO persuasive writing.

(forwward) Writes outreach sequences, prepares demos, handles objections, and manages pipelines with consultative selling frameworks. Triggers on cold outreach, demos, objection handling, CRM workflows, pipeline management, or any direct sales and customer acquisition activity.

(forwward) Runs customer discovery, builds ICPs, researches competitors, crafts positioning, and develops pricing with structured frameworks. Triggers on target customers, ICPs, competitor research, positioning, pricing, or strategic discovery conversations.

(forwward) Exports all stored memories, context, preferences, and instructions for migration to another AI platform. Triggers on platform migration, backing up AI context, auditing stored data, or setting up a new AI assistant with existing preferences.

(forwward) Writes clear, jargon-free technical documents through a structured discovery and drafting workflow. Interviews the user to determine document type, audience, and purpose before writing. Triggers on writing documentation, user guides, SOPs, runbooks, API docs, README files, process docs, decision records, release notes, or any request to document, explain, or write up something technical.

(forwward) Creates and maintains personal voice guidelines in the voice/ directory that content skills (/write, /gtm, /pcp-engine, /sales) use to match the user's authentic writing style. Triggers on voice setup, tone review, writing style editing, or when content output feels generic.

(forwward) Produces founder-voice blog posts, X/Twitter threads, and newsletters that sound like a real person sharing hard-won lessons, not a marketing department. Triggers on blog posts, threads, newsletters, content writing, or any founder-voice content.