build-like-amazon

Engineering process for solo founders and teams up to 50 engineers. Agents do architecture, code review, QA, and security. You make two decisions per feature.

Product team workflow: 18 skills + 4 research agents. Pre-dev planning with 5-gate (small features) and 10-gate (large features) orchestrators, delivery roadmap generation, delivery status tracking for evidence-based progress reporting, plus standalone streaming-event-mapping discovery. Includes parallel research agents, specialized code analysis, and Product Designer.

(forwward) Lean agent skills for building, shipping, strategy, and growth — no context bloat.

PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are set, launch plans are needed, or market positioning is discussed. Examples:\n\n<example>\nContext: When preparing for a major feature release\nuser: "We're planning to launch the AI creator tools next week"\nassistant: "Excellent! A major feature launch requires careful coordination. Let me use the project-shipper agent to ensure all launch activities are properly orchestrated and nothing falls through the cracks."\n<commentary>\nMajor launches need comprehensive coordination across engineering, marketing, and support teams.\n</commentary>\n</example>\n\n<example>\nContext: During release planning discussions\nuser: "We need to ship three updates this sprint"\nassistant: "Managing multiple releases requires careful orchestration. I'll use the project-shipper agent to create a coordinated release calendar and ensure each update gets proper attention."\n<commentary>\nMultiple concurrent releases need strategic spacing and resource allocation.\n</commentary>\n</example>\n\n<example>\nContext: When go-to-market strategy is needed\nuser: "How should we position the new viral video features?"\nassistant: "Positioning is crucial for feature adoption. Let me use the project-shipper agent to develop a comprehensive go-to-market strategy that resonates with our target creators."\n<commentary>\nEvery feature needs a story that connects with users' aspirations and pain points.\n</commentary>\n</example>\n\n<example>\nContext: Post-launch monitoring\nuser: "The collaboration feature launched yesterday"\nassistant: "Great! The critical first 48 hours determine success. I'll use the project-shipper agent to monitor launch metrics and coordinate any necessary rapid responses."\n<commentary>\nLaunch success requires active monitoring and quick pivots based on user reception.\n</commentary>\n</example>

Tools for creating and managing Claude Code plugins, agents, commands, and skills

Engineering + Product + Operations + Legal + Design + Data Science + Security Operations + Developer Experience + Infrastructure Specialist + AI Operations team — 100 agents as Claude Code specialists. Infrastructure, DevOps, backend, security, ML/AI, mobile, UX, analytics, growth, revenue, content, PR, customer success, finance, people, operations, support, contracts, compliance, IP, governance, regulatory, color systems, typography, motion, accessibility, design tokens, forecasting, feature engineering, model training, drift monitoring, vector search, LLM fine-tuning, pen testing, detection engineering, incident response, zero trust, API docs, SDK design, developer onboarding, Kubernetes, Terraform, FinOps, service mesh, edge computing, caching, queuing, multi-cloud, chaos engineering, model deployment, LLM evaluation, AI observability, guardrails, prompt engineering, embeddings, ranking, and more.